Merged
Conversation
Add push to protected CI job immediately after the previous push to protected CI job, meaning there shouldn't be any changes/new commits and so there shouldn't be any pushes. This, unfortunately, cannot be tested, but the outcome can be visually checked in the CI runs.
Add bash and git to the very bare alpine img.
CasperWA
force-pushed
the
close_27_check-commit-before-push
branch
from
373e098 to
1aa8e64
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #27.
Add push to protected CI job immediately after the previous push to protected CI job, meaning there shouldn't be any changes/new commits and so there shouldn't be any pushes.
This, unfortunately, cannot be tested, but the outcome can be visually checked in the CI runs.