-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: Allow messages after directives #1771
Comments
Use another comment (#) character. That is what I do. |
Resolved by @matthewpersico's solution, thanks! |
Apparently this no longer works? See https://github.com/gitpod-io/dockerfreeze/pull/54/checks?check_run_id=485963696 In tools/dockerfreeze line 6:
# shellcheck disable=SC2034 # FIXME: Are cmds used?
^-- SC1107: This directive is unknown. It will be ignored.
^-- SC1107: This directive is unknown. It will be ignored.
^-- SC1107: This directive is unknown. It will be ignored.
^-- SC1107: This directive is unknown. It will be ignored.
^-- SC1107: This directive is unknown. It will be ignored. |
Resolved: Github is using version: 0.4.6 which apparently does not support this |
JesterOrNot
pushed a commit
to Kreyren/dockerfreeze
that referenced
this issue
Mar 5, 2020
test test2 parse known issue final? final2? final3? sfdhgfsdh sdkgsfh sagasdg gjfghj dsgasd dgasdg dasgsag fdhdfsh fdhsfd dgadg rgfjdfgj dsgas dsgasdg dsagsdg Finally Resolve shellcheck hotfix for koalaman/shellcheck#1771 added bug(?) tracking Merge from investigation branch * sagsgda * test * sagsad * fdhs * dsgadsg * sagasdg * fhfgh * safa * sagsag * dsagasdg * ghdfg * adgsdg * ghgkhj * dsgasd * agsd * dgs * dsgasdg * dafsd * dsgasdg * dasgasdg * dasgasd sasag SAGSDAG gdfgj dgasdg asgasg dgasdg safasg gasdga gasdga sadsga dsgasdg dsgasdg reenable tests Removed cmds
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For bugs
For new checks and feature suggestions
Here's a snippet or screenshot that shows the problem:
Here's what shellcheck currently says:
Expected '=' after directive key. Fix any mentioned problems and try again. [SC1072]
Here's what I wanted or expected to see:
Expecting highlighted message to be valid for shellcheck
Reasoning: Less multi-line comments with reasoning to use
disable
directive compared to:Which i believe makes the code less readable especially when there is more comments above the code.
The text was updated successfully, but these errors were encountered: