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
Issue #215 is similar, and the answer is that I'm not entirely sure.
Convention is generally to not have a shebang.
Shellcheck would prefer having a shebang to determine the shell dialect.
A case can be made for using e.g. #!/bin/sh -n to enforce the non-executableness of the file while also letting shellcheck/file/apache/whatever determine the file type.
Maybe the solution is #220 's suggestion for making it easier to permanently ignore these errors, and/or changing the error to a info notification saying "This file has no shebang. Assuming bash."
If I'm writing files which are only intended to be sourced, never executed, should I have to include shebangs?
The text was updated successfully, but these errors were encountered: