docs(workflow): depends-on spans a repository owner, not an organization - #12717
Merged
mergify[bot] merged 1 commit intoSep 9, 2026
Conversation
Member
Author
|
This pull request is part of a Mergify stack:
|
This was referenced Sep 7, 2026
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. |
There was a problem hiding this comment.
🟢 Approval recommended
The change is a small, low-risk docs clarification that matches the documented behavior elsewhere and introduces no internal-information leaks in the edited content.
Pull request overview
Updates the “Pull Request Dependencies” documentation for the merge workflow action to correctly describe the scope and failure behavior of Depends-On: references, aligning it with the already-corrected rules documented under merge protections.
Changes:
- Clarifies that cross-repository dependencies are limited to the same repository owner (user or organization), not “within your organization”.
- Documents that unresolvable references do not get skipped and will keep the merge blocked until corrected, including examples of unresolvable cases.
File summaries
| File | Description |
|---|---|
| src/content/docs/workflow/actions/merge.mdx | Corrects Depends-On: scope (same repository owner) and explains blocking behavior for unresolvable references. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
jd
marked this pull request as ready for review
September 8, 2026 11:32
The Pull Request Dependencies section said a `Depends-On:` header could point at "other repositories with Mergify installed within your organization". The constraint is the same repository *owner*, which may be a user account rather than an organization. A reference to another owner is rendered with a "depends-on conditions must have the same repository owner" warning and never satisfies. The section was also silent on what happens to a reference Mergify cannot resolve — another owner, a repository without Mergify, or a pull request that does not exist. None of those ever reach the `depends-on` attribute, so the condition stays unsatisfied and blocks the merge rather than being skipped, which is the behaviour a reader most needs to be told about. This brings the page in line with the same rules already documented for the `depends-on` merge protection in /merge-protections/builtin, which was corrected and left this page behind. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019V4gXwb2UucysW4xmB7bAw Change-Id: I790b2c0c6e38ed5eff9ac587378765c72939f264
jd
force-pushed
the
devs/jd/jd/recover-actions-corrections/depends-spans-repo-owner-organization--790b2c0c
branch
from
September 8, 2026 12:39
8a22459 to
550933e
Compare
Member
Author
Revision history
|
Member
Author
|
Force-pushed, but nothing changed on this pull request — the stack was rebased on Compare: |
kozlek
approved these changes
Sep 9, 2026
remyduthu
approved these changes
Sep 9, 2026
Contributor
Merge Queue Status
This pull request spent 5 minutes 48 seconds in the queue, including 2 minutes 20 seconds running CI. Required conditions to merge
|
63 tasks
63 tasks
mergify
Bot
deleted the
devs/jd/jd/recover-actions-corrections/depends-spans-repo-owner-organization--790b2c0c
branch
September 9, 2026 08:18
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 Pull Request Dependencies section said a
Depends-On:header could pointat "other repositories with Mergify installed within your organization". The
constraint is the same repository owner, which may be a user account rather
than an organization. A reference to another owner is rendered with a
"depends-on conditions must have the same repository owner" warning and never
satisfies.
The section was also silent on what happens to a reference Mergify cannot
resolve — another owner, a repository without Mergify, or a pull request that
does not exist. None of those ever reach the
depends-onattribute, so thecondition stays unsatisfied and blocks the merge rather than being skipped,
which is the behaviour a reader most needs to be told about.
This brings the page in line with the same rules already documented for the
depends-onmerge protection in /merge-protections/builtin, which wascorrected and left this page behind.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_019V4gXwb2UucysW4xmB7bAw