docs(workflow): completes the list of conditions the merge action injects - #12946
Open
mergify-ci-bot wants to merge 1 commit into
Conversation
Contributor
Merge Protections🔴 2 of 5 protections blocking · waiting on 👀 reviews
🔴 👀 Review RequirementsWaiting for
This rule is failing.
🔴 🔎 ReviewsWaiting for
This rule is failing.
Show 3 satisfied protections🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
jd
previously approved these changes
Sep 23, 2026
mergify-ci-bot
force-pushed
the
docs-agent/health-audit-workflow-2--merge-action-injected-conditions
branch
from
September 23, 2026 10:51
f8d1263 to
021fee5
Compare
mergify-ci-bot
force-pushed
the
docs-agent/health-audit-workflow-2--merge-action-injected-conditions
branch
from
October 2, 2026 22:15
021fee5 to
1b8334d
Compare
Contributor
Author
|
This branch had an error being 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
mergeaction page opens with the list of conditions Mergify adds to whateveryou wrote yourself, and two entries were off.
Merge protections were missing entirely. The engine builds the merge action's
minimum conditions from a shared helper that, when the Merge Protections product is
enabled on the repository, appends a requirement on the merge protections gate: a
check-run or a deployment, depending on
merge_protections_settings.reporting_method. Someone reading this list to work outwhy a
mergeaction is not firing would not have found the answer here.The configuration-change entry said Mergify merges configuration changes "by
default", which reads as though a setting exists to turn that off. The setting that
used to do it is gone from the configuration schema, and the engine drops it from
configurations that still carry it. The behavior itself is unchanged, so the entry
now states it without implying a knob.
There is also a last entry for
method: fast-forward, which injects#commits-behind = 0on top of the shared minimum conditions, and a note on whatthe merge protections entry does not cover. A scheduled freeze decides the merge
protections check only when the merge queue is off; with the queue enabled, the
freeze is reported in that check but enforced by the queue, so the check can pass
while a freeze is running and the
mergeaction goes ahead.Evidence: the merge action's minimum conditions helper in the engine, which carries
no freeze condition of its own; the merge protections evaluator, which leaves freeze
rules out of the check conclusion when the merge queue product is enabled and keeps
them for reporting; and the configuration schema.