Skip to content

docs(merge-protections): documents the two other things that stop auto_merge_conditions working - #13050

Merged
mergify[bot] merged 1 commit into
Mergifyio:mainfrom
mergify-ci-bot:docs-agent/health-audit-merge-protections--auto-merge-constraints-omit-two-blockers
Sep 29, 2026
Merged

mergify[bot] merged 1 commit into
Mergifyio:mainfrom
mergify-ci-bot:docs-agent/health-audit-merge-protections--auto-merge-constraints-omit-two-blockers

Conversation

@mergify-ci-bot

@mergify-ci-bot mergify-ci-bot commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

The Constraints section listed what auto_merge_conditions cannot be combined
with, but not what it requires. Enabling it on a repository that does not have
Merge Protections turned on is accepted by the configuration validator and then
does nothing at all — the engine checks the product is enabled before it acts,
independently of whether a merge queue exists. That is a quiet failure: the
configuration is valid, no error is reported, and pull requests simply are not
merged.

Adds a sentence stating the prerequisite and pointing at the page that covers
enabling the product.

Evidence: the engine's auto-merge gate, which returns false unless Merge
Protections is among the repository's enabled products.

@mergify
mergify Bot had a problem deploying to Mergify Merge Protections September 28, 2026 22:24 Failure
@mergify

mergify Bot commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

Merge Protections

🟢 All 5 merge protections satisfied — ready to merge.

Show 5 satisfied protections

🟢 👀 Review Requirements

  • any of:
    • #approved-reviews-by >= 1
    • author = dependabot[bot]
    • author = renovate[bot]
    • all of:
      • -head ~= ^docs-agent/
      • author = mergify-ci-bot

🟢 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)(?:\(.+\))?!?:

🟢 🔎 Reviews

  • #changes-requested-reviews-by = 0
  • #review-requested = 0
  • #review-threads-unresolved = 0

🟢 📕 PR description

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

🟢 🚦 Auto-queue

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

@mergify
mergify Bot requested a review from a team September 28, 2026 22:27
Comment thread src/content/docs/merge-protections/auto-merge.mdx
@mergify
mergify Bot requested a review from a team September 29, 2026 04:26
jd
jd previously requested changes Sep 29, 2026

@jd jd left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

see Julian commentsee Julian comment

@mergify-ci-bot
mergify-ci-bot force-pushed the docs-agent/health-audit-merge-protections--auto-merge-constraints-omit-two-blockers branch from 2f30427 to db1d580 Compare September 29, 2026 10:53
@mergify
mergify Bot dismissed jd’s stale review September 29, 2026 10:54

Pull request has been modified.

@mergify
mergify Bot deployed to Mergify Merge Protections September 29, 2026 10:54 Active
@mergify-ci-bot

Copy link
Copy Markdown
Contributor Author

🤖 I read this review and pushed a new revision.

Trimmed, per Julian's point. The paragraph about the deprecated auto_merge
boolean and its migration pull request is gone, and the autoqueue sentence is
restored to what it says on main.

The diff is now a single added paragraph: auto_merge_conditions only takes
effect when Merge Protections is enabled on the repository, with or without a
merge queue. That one is worth keeping — it is a constraint on the key the page
is about, not on a key being retired, and it is the quiet failure mode where the
configuration validates and then nothing happens.

@mergify
mergify Bot requested a review from a team September 29, 2026 10:56
@mergify

mergify Bot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 3 minutes 1 second in the queue, including 2 minutes 41 seconds running CI.

Required conditions to merge

@mergify mergify Bot added the queued label Sep 29, 2026
@mergify
mergify Bot merged commit 84d03f0 into Mergifyio:main Sep 29, 2026
12 checks passed
@mergify mergify Bot removed the queued label Sep 29, 2026

This branch was successfully deployed

1 active deployment
Mergify Merge Protections — db1d580c Deployed Sep 29, 2026 by mergify[bot]
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.

5 participants