Repository navigation
docs(workflow): recapture the branch protection injection shot on the merge action page - #13260
Merged
mergify[bot] merged 1 commit intoOct 7, 2026
Conversation
… merge action page The screenshot under "Branch Protection Conditions" showed `#approved-reviews-by>=1` and `#changes-requested-reviews-by=0` tagged [GitHub branch protection]. Mergify no longer injects either: a branch protection that requires an approving review now injects the single `github-review-approved` condition the paragraph above the image already describes. The new shot is a merge rule in the Mergify Summary check on the public mergify-sandbox/docs-captures repository, for a pull request targeting a branch whose protection requires one approving review. It shows `github-review-approved` with its [GitHub branch protection] tag, the merge requirements and the configuration change block. The alt text now says what the image shows. Fixes Mergifyio/ci-bot#685 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Change-Id: I01fd5cc0da57c414584171bf4e2180318fea8a51
Contributor
Merge Protections🟢 All 5 merge protections satisfied — ready to merge. Show 5 satisfied protections🟢 👀 Review Requirements
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
jd
marked this pull request as ready for review
October 7, 2026 07:24
kozlek
approved these changes
Oct 7, 2026
Contributor
Merge Queue Status
This pull request spent 3 minutes 14 seconds in the queue, including 2 minutes 43 seconds running CI. Required conditions to merge
|
36 of 49 tasks
mergify
Bot
deleted the
devs/jd/jd/issue-685/recapture-branch-protection-injection-shot-merge--01fd5cc0
branch
October 7, 2026 07:32
This branch was successfully deployed
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.
The screenshot under "Branch Protection Conditions" showed
#approved-reviews-by>=1and#changes-requested-reviews-by=0tagged[GitHub branch protection]. Mergify no longer injects either: a branch
protection that requires an approving review now injects the single
github-review-approvedcondition the paragraph above the image alreadydescribes.
The new shot is a merge rule in the Mergify Summary check on the public
mergify-sandbox/docs-captures repository, for a pull request targeting a
branch whose protection requires one approving review. It shows
github-review-approvedwith its [GitHub branch protection] tag, themerge requirements and the configuration change block. The alt text now
says what the image shows.
Fixes Mergifyio/ci-bot#685
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com