Check if *-MAlonzo branch exists on each run
#609
Merged
Conversation
This file contains 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
Lucsanszky
force-pushed
the
ldan/ga-improvement
branch
7 times, most recently
from
c6b592c
to
7bd7fc6
Compare
Lucsanszky
force-pushed
the
ldan/ga-improvement
branch
from
7bd7fc6
to
bc9ba7d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
By checking the existence of the automatically created
*-MAlonzobranch on each workflow run and creating the branch if the check fails, rather than only running the branch creation on PR open events, we are reducing the likelihood of missing the branch creation as happened in #607. The*-MAlonzobranch creation step was skipped there for some reason (probably an issue with one of the webhooks in theifcheck that should have triggered the step) which caused some problems down the line.Checklist
CHANGELOG.md