Skip to content

docs(agent): Depends-On is scoped by repository owner, not organization - #12631

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

docs(agent): Depends-On is scoped by repository owner, not organization#12631
mergify[bot] merged 1 commit into
Mergifyio:mainfrom
mergify-ci-bot:docs-agent/health-audit-merge-protections

Conversation

@mergify-ci-bot

@mergify-ci-bot mergify-ci-bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

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 Reason is
required and was missing from the steps entirely; the two datetime fields are
From and To under a Schedule heading, not "start / end". The page also
said 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.

@mergify
mergify Bot had a problem deploying to Mergify Merge Protections August 31, 2026 22:35 Failure
@mergify

mergify Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Merge Protections

🟢 All 6 merge protections satisfied — ready to merge.

Show 6 satisfied protections

🟢 🤖 Continuous Integration

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

🟢 👀 Review Requirements

  • any of:
    • #approved-reviews-by >= 2
    • 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 August 31, 2026 22:38
Comment thread src/content/docs/merge-protections/auto-merge.mdx Outdated
@mergify
mergify Bot requested a review from a team September 1, 2026 05:56
jd
jd previously approved these changes Sep 1, 2026
@mergify
mergify Bot requested a review from a team September 1, 2026 05:57
@mergify-ci-bot
mergify-ci-bot force-pushed the docs-agent/health-audit-merge-protections branch from 26ed7a0 to b991f26 Compare September 1, 2026 10:27
@mergify
mergify Bot dismissed jd’s stale review September 1, 2026 10:27

Pull request has been modified.

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

Copy link
Copy Markdown
Contributor Author

🤖 I read this review and pushed a new revision.

@mergify
mergify Bot requested a review from a team September 1, 2026 11:56
@mergify

mergify Bot commented Sep 1, 2026

Copy link
Copy Markdown
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

@mergify mergify Bot added the queued label Sep 1, 2026
@mergify
mergify Bot merged commit 395f6b9 into Mergifyio:main Sep 1, 2026
9 checks passed
@mergify mergify Bot removed the queued label Sep 1, 2026
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.

4 participants