Skip to content

Conversation

@williamh
Copy link
Contributor

@williamh williamh commented Oct 9, 2021

No description provided.

*) continue ;;
esac
echo "Checking ${shellscript} with shellcheck:"
shellcheck -s sh "${shellscript}" || true
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this ignores all errors, so this job will never fail. since it will always be green (in the actions tab, and in PRs), no one will ever look at it. so like, what's the point ? :)

i think you want to set ret=0 at the top of the file, change this true to ret=1, and then exit ${ret} at the bottom.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ultimately, my thought is to change the "true" to "exit" to bail immediately once a script fails shellcheck, but I can't do that yet because I'll need to figure out which messages are false positives so they can be turned off in a configuration file or in the source files themselves.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

none of the CI checks block merges or pushes, so i think it'd be OK to just land this as-is. but i'm fine with an exit 0 at the end of the script with a TODO explaining why it's ignoring the $ret if you want to go that route.

Copy link
Member

@vapier vapier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should prob resolve all open conversations ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants