docs(agent): Depends-On is scoped by repository owner, not organization - #12631
Merged
mergify[bot] merged 1 commit intoSep 1, 2026
Conversation
Contributor
Merge Protections🟢 All 6 merge protections satisfied — ready to merge. Show 6 satisfied protections🟢 🤖 Continuous Integration
🟢 👀 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
reviewed
Sep 1, 2026
jd
previously approved these changes
Sep 1, 2026
mergify-ci-bot
force-pushed
the
docs-agent/health-audit-merge-protections
branch
from
September 1, 2026 10:27
26ed7a0 to
b991f26
Compare
Contributor
Author
|
sileht
approved these changes
Sep 1, 2026
AlexandreGaubert
approved these changes
Sep 1, 2026
Contributor
Merge Queue Status
This pull request spent 3 minutes 25 seconds in the queue, including 2 minutes 37 seconds running CI. Required conditions to merge
|
63 tasks
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 built-in Depends-On protection is scoped by the repository owner, personal
account or organization alike, but the page said "the same organization". The
engine compares the owner login, and the message it shows a user says "same
repository owner" in as many words. Two neighbouring claims were wrong the same
way: an unresolvable reference (a repository without Mergify, a pull request
that does not exist) fails the protection rather than waiting on it, and the
merge queue's dependency display covers same-repository stack predecessors
only, not every same-repository dependency as the old wording implied.
The Scheduled Freeze walkthrough had drifted from the form it describes. The
sub-section is called Scheduled Freezes, not Freezes;
Freeze Reasonisrequired and was missing from the steps entirely; the two datetime fields are
FromandTounder aScheduleheading, not "start / end". The page alsosaid the protections check stays pending during a freeze without noting that is
the case without the merge queue.
Setup and Custom Rules contradicted each other about where rules live, one
saying the dashboard and the other the configuration file. Both are true: the
dashboard's rule builder is an editor that opens a pull request against the
configuration file, and each page now says so.
The freeze page also gains a recurring-window recipe, because a freeze covers
one window and never repeats, which the page never said.
Evidence: the depends-on condition builder and the freeze rule construction in
the engine, the scheduled-freeze form and sidebar in the dashboard, and the
published configuration schema.
Open question: whether the three screenshots on the setup and freeze pages still
match the form. Every prose correction above points to a walkthrough written
against an older UI, and those images were captured alongside it, but I cannot
see an image or reach the dashboard to check.