ci: fix sync job failing when release-candidate has no branch protection rules#82
Merged
Merged
Conversation
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions job sync
ci: fix sync job failing when release-candidate has no branch protection rules
Jul 17, 2026
ToonCasteele
marked this pull request as ready for review
July 17, 2026 11:43
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.
gh pr merge --auto --mergerequires branch protection rules on the target branch. Sincerelease-candidatehas none, every run of the "Promote main to release candidate" workflow was failing withPull request Protected branch rules not configured for this branch (enablePullRequestAutoMerge).Changes
.github/workflows/promote-main-to-release-candidate.yml: wrap the auto-merge call in a fallback — attempt--auto --mergefirst; if it fails (no branch protection), fall back to a direct--merge.The conflict-detection and Copilot conflict-resolution paths are unchanged.
Target branch
release-candidate.main.