docs(merge-protections): documents the two other things that stop auto_merge_conditions working - #13050
Conversation
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
left a comment
There was a problem hiding this comment.
see Julian commentsee Julian comment
…o_merge_conditions working
2f30427 to
db1d580
Compare
Trimmed, per Julian's point. The paragraph about the deprecated The diff is now a single added paragraph: |
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
|
The Constraints section listed what
auto_merge_conditionscannot be combinedwith, 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.