Repository navigation
fix(ci): open a release PR instead of pushing to protected main - #13968
Merged
Merged
Conversation
4 tasks
This was referenced Aug 10, 2026
Closed
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
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.
Thinking Path
The
Sync Dev_new_gui → mainworkflow has never completed. Two independent blockers, discovered one behind the other:Blocked on divergence — the 2026-08-05 run:
Fixed by #13951, which merged
main's history back into the trunk (zero content change).Then blocked on branch protection — today's run, having passed the divergence gate:
mainrequires two status checks —No open blocks-merge issues reference this PRandNo commit trailers. A direct push moves the branch to a commit that carries neither, so the hook declines it. That is not a misconfiguration to work around; it is the protection doing its job. The push could never have succeeded, which is whymainsat 41 commits behind for days with no visible signal — a dispatch-only workflow failing silently is invisible unless someone goes looking.So the step routes through a PR instead, which is what lets the required checks run against the release head. #13816 did exactly this by hand on 2026-08-09 — this makes the builtin do what the human already had to.
What Changed
.github/workflows/sync-main-to-dev.ymlonly.release-sync-mainbranch to the trunk, then open a PR intomainenv:(it readif [ "0" != "0" ]in the log — correct, but interpolated rather than passed)main, and the step carries theGH006output so the next reader does not rediscover itStill
workflow_dispatch-only, still requires typingrelease. Merging the PR is the release; this only makes the PR appear.Verification
The
run:block was extracted from the YAML and exercised withgitandghstubbed — a workflow edit that merely looks right is what produced the original bug.maindiverged (BEHIND=3)::error::main has 3 commit(s) not in Dev_new_gui— refuses, unchangedrelease-sync-main, creates the PR, writesurl=to$GITHUB_OUTPUT#4242, creates no duplicateThe PR body is written via a file and de-indented, so the YAML block indentation does not leak into it:
Not verified end to end: the workflow itself has not been re-dispatched against this change — it can only be tested by running it, and doing that from a branch would open a real release PR. Worth dispatching once this lands.
Refs #2445
Model Used
Opus 5