You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@ See the [license file](LICENSE)
46
46
47
47
Add bash-lib into your project in the way that best fits your workflow. The only requirement is that you **pin the version of
48
48
bash-lib that you use**. This is important so that changes to bash-lib do not have the power to break all projects that use
49
-
bash-lib. Your project can then test updates to bash-lib and roll forward periodicly.
49
+
bash-lib. Your project can then test updates to bash-lib and roll forward periodically.
50
50
51
51
Options:
52
52
* Add a submodule: they are an easy way to integrate bash-lib and automatically use a single SHA until manually updated. Submodules add a pointer from a mount point in your repo to the external repo (bash-lib), and require workflow changes to ensure that pointer is derferenced during clone, checkout and some other opertaions.
0 commit comments