-
Notifications
You must be signed in to change notification settings - Fork 137
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
ci-checks: run all the checks on checked-in files; check shellcheck #175
Conversation
@mmlb do you think it is worth adding |
I'm fine with adding git to shell.nix. The shell.nix's aren't super pure for the projects and I've kind of wanted to move towards that way as much as possible where it makes sense. |
Don't run on files which are not being committed, and run all the checks even if one step failed
if [ $? -eq 0 ]; then | ||
break | ||
fi | ||
while ! docker login -u username -p password localhost; do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this really belong in this PR? I'm fine if you want to earmark it in, just wand to double check.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe not, it just seemed like the easiest fix for $i
being unused. I could swap it out to just echo the iteration. What do you think?
Don't run on files which are not being committed, and run all
the checks even if one step failed.
This PR should fail (validating that the CI check still fails) and then I will add additional commits fixing its complaints.