ci: Disable GitHub merge button (maintainers land changes via Copybara)#6086
Closed
Jacksunwei wants to merge 4 commits into
Closed
ci: Disable GitHub merge button (maintainers land changes via Copybara)#6086Jacksunwei wants to merge 4 commits into
Jacksunwei wants to merge 4 commits into
Conversation
Adds an always-failing required check so the GitHub merge button stays disabled on every PR. Changes are submitted through Piper CL, not merged via GitHub. The job runs standalone and does not block or gate other CI checks; it only keeps the merge button grayed out via a branch ruleset that requires this check. Change-Id: I28524399b467cd5c2c237331c6ea85e71d1ddc94
Rename the workflow and job so the PR checks row reads as an instruction
("Do Not Merge on GitHub / Submit via Piper CL"), and expand the error
annotation to explain the mirror/Piper flow.
Change-Id: I1fa1408bed9dab4cc4b49434183776006f011417
Update the check name and annotation to clarify that maintainers land changes internally and Copybara syncs them back, rather than merging on GitHub. Change-Id: I7add290fcc17125014ebcbee5ce00d02fd359f17
Jacksunwei
changed the title
Rename the job so the PR check row reads "Do Not Merge on GitHub / maintainers will submit via Copybara". Change-Id: I6b186ef0e02fd189edb5d8db071429fb61dda72f
copybara-service Bot
pushed a commit
that referenced
this pull request
Jun 11, 2026
Merge #6086 ## Summary - Adds `.github/workflows/block-merge.yml`, an always-failing check that keeps the GitHub merge button disabled on every PR. - Maintainers land changes internally and Copybara syncs them back to this repo; PRs are not merged through the GitHub UI. - The job runs standalone (no `needs:` dependents) so it does **not** block or cancel other CI checks — they still run and report normally. On the PR page the check appears as: > **Do Not Merge on GitHub / Do not merge — maintainers land changes via Copybara** with the annotation: > Do NOT merge this pull request on GitHub. A maintainer will land the change internally, and Copybara will sync it back to this repository automatically. ## Follow-up (manual, GitHub UI) After this merges, create a branch ruleset to require the check: 1. Settings → Rules → Rulesets → **New branch ruleset** 2. Name: `Block GitHub Merge`, Enforcement: **Active** 3. Target branches → **Include default branch** 4. Rules → **Require status checks to pass** → add check **`Do not merge — maintainers land changes via Copybara`** 5. **Create** The check name appears in the picker after this workflow runs once; otherwise type it manually. ## Test plan - [ ] Confirm the merge-block check appears and fails on this PR - [ ] Confirm other CI checks still run and report independently - [ ] After ruleset is added, confirm the merge button is grayed out Co-authored-by: Wei Sun (Jack) <weisun@google.com> COPYBARA_INTEGRATE_REVIEW=#6086 from google:ci/block-github-merge 587a03a PiperOrigin-RevId: 930808152
Collaborator
|
Thank you @Jacksunwei for your contribution! 🎉 Your changes have been successfully imported and merged via Copybara in commit f4743cd. Closing this PR as the changes are now in the main branch. |
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
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.
Summary
.github/workflows/block-merge.yml, an always-failing check that keeps the GitHub merge button disabled on every PR.needs:dependents) so it does not block or cancel other CI checks — they still run and report normally.On the PR page the check appears as:
with the annotation:
Follow-up (manual, GitHub UI)
After this merges, create a branch ruleset to require the check:
Block GitHub Merge, Enforcement: ActiveDo not merge — maintainers land changes via CopybaraThe check name appears in the picker after this workflow runs once; otherwise type it manually.
Test plan