ci(release): make main sync best-effort so tags publish unblocked - #323
Merged
Conversation
The main-protected ruleset added in #313 (pull_request + required_status_checks, no bypass actors) rejects the sync job's direct force-push to main, which gated every downstream job — no binaries, no ghcr image, no GitHub release. Mark the job continue-on-error so releases ship; main sync stays documented as an admin follow-up.
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
1 participant
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.
What
Adds
continue-on-error: trueto thesync-mainjob inrelease.ymlwith a comment documenting why.Why
The
main-protectedruleset added in #313 (requires PRs + 10 status checks, no bypass actors) rejects the job's directgit push HEAD:main --force. Becausebuild-release, the Docker jobs, and the GitHub Release job all hadneeds: sync-main, one rejected push silently blocked the entire release: thev0.3.0tag run (#33734057649) failed at sync-main and skipped every build. With the job marked best-effort, tag pushes always produce binaries, theghcr.io/codecoradev/trapfallimage, and the release; themainsync failure stays visible as an expected failure until an admin allows the automation under Settings → Rules → Rulesets.Testing
actionlint-style structure unchanged (job-level flag, no step edits)