-
Notifications
You must be signed in to change notification settings - Fork 169
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
style(bash): added decision to start using bash style guide [ci skip]
- Loading branch information
Maurice Faber
committed
Nov 6, 2020
1 parent
f75a878
commit e43b4e3
Showing
2 changed files
with
17 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
Maurice: | ||
|
||
Seeing we have too many discussions around bash best practices we will settle for a style guide. | ||
I don't see a point in discussing which one to choose, only to choose one that is used by very big corporation/community. | ||
That is why I chose to start using this one: | ||
|
||
https://google.github.io/styleguide/shellguide.html | ||
|
||
Exceptions: | ||
|
||
- Keep file extensions for many reasons: easy for humans, ootb detection for most editors | ||
|
||
NOTE: | ||
|
||
Added flags to shell-format extension: "-i 2 -ci" to come close according to https://emacs.stackexchange.com/questions/32151/linter-for-google-shell-style-guide |