Skip to content

fix(mergify): drop docs default review requirement to one approval - #12769

Open
jd wants to merge 1 commit into
mainfrom
devs/jd/jd/docs-single-approval/drop-docs-default-review-requirement-one-approval--9983de27
Open

fix(mergify): drop docs default review requirement to one approval#12769
jd wants to merge 1 commit into
mainfrom
devs/jd/jd/docs-single-approval/drop-docs-default-review-requirement-one-approval--9983de27

Conversation

@jd

@jd jd commented Sep 10, 2026

Copy link
Copy Markdown
Member

Review Requirements' DefaultReviewCond anchor required
#approved-reviews-by >= 2; drop it to 1 so a single approval is
enough to merge on Mergifyio/docs, for everyone, not another
carve-out.

DefaultReviewCond is shared by the Hotfix Review Requirements
protection (or: *DefaultReviewCond) and by the request-review
pull request rule, so both move with it. That also makes the
hotfix-specific hotfix Review Requirements' escapes dead: its
eng-mgr-with-one-approval and devs-with-eng-mgr-or-fix/revert-title
branches only ever granted "one approval clears review", which the
new default already grants to any author. Removed them along with
the now-redundant label != hotfix guard in the request-review
rule's condition, which existed only to avoid double-counting that
escape.

Checked the repo's GitHub side: of its 9 rulesets, only "Require
pull request for default branch" carries a pull_request rule, and
its required_approving_review_count is 0 — no ruleset conflicts
with the new threshold.

Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com

Review Requirements' DefaultReviewCond anchor required
#approved-reviews-by >= 2; drop it to 1 so a single approval is
enough to merge on Mergifyio/docs, for everyone, not another
carve-out.

DefaultReviewCond is shared by the Hotfix Review Requirements
protection (`or: *DefaultReviewCond`) and by the request-review
pull request rule, so both move with it. That also makes the
hotfix-specific hotfix Review Requirements' escapes dead: its
eng-mgr-with-one-approval and devs-with-eng-mgr-or-fix/revert-title
branches only ever granted "one approval clears review", which the
new default already grants to any author. Removed them along with
the now-redundant `label != hotfix` guard in the request-review
rule's condition, which existed only to avoid double-counting that
escape.

Checked the repo's GitHub side: of its 9 rulesets, only "Require
pull request for default branch" carries a pull_request rule, and
its required_approving_review_count is 0 — no ruleset conflicts
with the new threshold.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Change-Id: I9983de27602a153f5510b61cc8bb5c91a86e7705
Copilot AI lite review requested due to automatic review settings September 10, 2026 18:58
@mergify
mergify Bot had a problem deploying to Mergify Merge Protections September 10, 2026 18:58 Failure
@mergify

mergify Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Merge Protections

🔴 2 of 7 protections blocking · waiting on 👀 reviews

Protection Waiting on
🔴 👀 Review Requirements 👀 reviews
🔴 🔎 Reviews 👀 reviews
🟢 📃 Configuration Change Requirements
🟢 🤖 Continuous Integration
🟢 Enforce conventional commit
🟢 📕 PR description
🟢 🚦 Auto-queue

🔴 👀 Review Requirements

Waiting for

  • #approved-reviews-by >= 2
This rule is failing.
  • any of:
    • #approved-reviews-by >= 2
    • author = dependabot[bot]
    • author = renovate[bot]
    • all of:
      • author = mergify-ci-bot
      • -head ~= ^docs-agent/

🔴 🔎 Reviews

Waiting for

  • #review-requested = 0
This rule is failing.
  • #review-requested = 0
  • #changes-requested-reviews-by = 0
  • #review-threads-unresolved = 0

Show 5 satisfied protections

🟢 📃 Configuration Change Requirements

Mergify configuration change

  • any of:
    • check-success = @mergify/Configuration changed
    • check-success = @mergify/Configuration has been deleted

🟢 🤖 Continuous Integration

  • all of:
    • check-success = build
    • check-success = diagram-tokens
    • check-success = lint
    • check-success = test
    • any of:
      • check-success = test-broken-links
      • label = ignore-broken-links
    • any of:
      • check-success=Cloudflare Pages
      • -head-repo-full-name~=^Mergifyio/

🟢 Enforce conventional commit

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?:

🟢 📕 PR description

  • body ~= (?ms:.{48,})

🟢 🚦 Auto-queue

When all merge protections are satisfied, this pull request will be queued automatically.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

It changes merge governance (required approvals) and should be explicitly confirmed by a human reviewer for policy/impact alignment.

Pull request overview

This PR updates the repository’s Mergify configuration to reduce the default approval threshold from two approvals to one, and removes now-redundant hotfix-specific review “escape” logic that previously existed to allow one-approval merges in limited cases.

Changes:

  • Lower DefaultReviewCond from #approved-reviews-by >= 2 to >= 1.
  • Remove the dedicated hotfix review-escape conditions (&HotfixReviewCond) and simplify hotfix protections to reuse *DefaultReviewCond.
  • Simplify the “request review” pull request rule by removing the hotfix-specific guard and relying solely on not: or: *DefaultReviewCond.
File summaries
File Description
.mergify.yml Adjusts default review success conditions and simplifies hotfix and review-request logic accordingly.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@mergify
mergify Bot requested a review from a team September 10, 2026 19:02
@jd
jd marked this pull request as ready for review September 11, 2026 07:00
@mergify
mergify Bot requested a review from a team September 11, 2026 07:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants