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
shell-scripts input was implemented initially as the only way to identify shell scripts for scanning. Since then, Differential ShellCheck evolved, and it can now detect shell scripts automatically.
Hence, shell-scripts will be removed in the next version.
Describe the solution you'd like
No response
The text was updated successfully, but these errors were encountered:
jamacku
changed the title
[ANNOUNCEMENT]: input ignored-codes is going to be dropped in next release 🚫
[ANNOUNCEMENT]: input shell-scripts is going to be dropped in next release 🚫
Aug 9, 2023
jamacku
added a commit
to jamacku/differential-shellcheck
that referenced
this issue
Aug 9, 2023
`shell-scripts` input was implemented initially as the only way to identify
shell scripts for scanning. Since then, Differential ShellCheck evolved,
and it can now detect shell scripts automatically.
Hence, `shell-scripts` will be removed in the next version.
Fixes: redhat-plumbers-in-action#287
`shell-scripts` input was implemented initially as the only way to identify
shell scripts for scanning. Since then, Differential ShellCheck evolved,
and it can now detect shell scripts automatically.
Hence, `shell-scripts` will be removed in the next version.
Fixes: redhat-plumbers-in-action#287
`shell-scripts` input was implemented initially as the only way to identify
shell scripts for scanning. Since then, Differential ShellCheck evolved,
and it can now detect shell scripts automatically.
Hence, `shell-scripts` will be removed in the next version.
Fixes: #287
Type of issue
other
Description
shell-scripts
input was implemented initially as the only way to identify shell scripts for scanning. Since then, Differential ShellCheck evolved, and it can now detect shell scripts automatically.Hence,
shell-scripts
will be removed in the next version.Describe the solution you'd like
No response
The text was updated successfully, but these errors were encountered: