Uh oh!
There was an error while loading. Please reload this page.
[v3-3-test] Fix scheduled CI upgrade failing when its PR already exists (#69018) - #69055
Merged
Conversation
…ts (#69018) The scheduled "breeze ci upgrade" job force-pushes a stable branch (ci-upgrade-<branch>) and then looks for an existing PR before creating one. The lookup passed the "owner:branch" head label to "gh pr list --head", but that flag filters by the bare branch name only and does not support the "owner:branch" syntax, so the existing PR was never found and the job fell through to "gh pr create" — which rejected the duplicate and failed the run. Use the bare branch name for the "gh pr list" and "gh pr ready" lookups (only "gh pr create --head" needs the cross-fork "owner:branch" label), and treat an "already exists" creation error as success since the branch has already been force-pushed. (cherry picked from commit 419ac06) Co-authored-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
1 task
potiuk
marked this pull request as ready for review
June 26, 2026 20:42
potiuk
requested review from
amoghrajesh, ashb, bugraoz93, choo121600, ephraimbuddy, gopidesupavan, jason810496, jedcunningham, jscheffl, potiuk and vatsrahul1001
as code ownersJune 26, 2026 20:42
Uh oh!
There was an error while loading. Please reload this page.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The scheduled "breeze ci upgrade" job force-pushes a stable branch
(ci-upgrade-) and then looks for an existing PR before creating
one. The lookup passed the "owner:branch" head label to "gh pr list
--head", but that flag filters by the bare branch name only and does not
support the "owner:branch" syntax, so the existing PR was never found and
the job fell through to "gh pr create" — which rejected the duplicate and
failed the run.
Use the bare branch name for the "gh pr list" and "gh pr ready" lookups
(only "gh pr create --head" needs the cross-fork "owner:branch" label),
and treat an "already exists" creation error as success since the branch
has already been force-pushed.
(cherry picked from commit 419ac06)
Co-authored-by: Shahar Epstein 60007259+shahar1@users.noreply.github.com