Backport of chore(ci): fix backport assistant branch creation race into release/1.13.x #17251
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
hc-github-team-consul-core
force-pushed
the
backport/dans/fix-backport-assistant-race/internally-picked-griffon
branch
from
5a9609e to
a7460ad
Compare
github-actions
bot
added
theme/contributing
github-team-consul-core-pr-approver
approved these changes
May 8, 2023
hc-github-team-consul-core
deleted the
backport/dans/fix-backport-assistant-race/internally-picked-griffon
branch
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.
Backport
This PR is auto-generated from #17249 to be assessed for backporting due to the inclusion of the label backport/1.13.
The below text is copied from the body of the original PR.
Description
A new patch for
backport-assistantwas released to deal with a race in creating the new branch and pushing the PR. For a single PR, this may appear as an error pushing a reference that doesn't exist. For multiple backports, I suspect that it manifests itself as applying the cherry-picked commits on top of the previously checked-out branch.Overview of commits