Confirmation message for Depends-On:
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 339
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behavior
Sometimes the changes for feature/B depend on the changes for feature/A. The Depends-On: #1234 syntax allows me to block merging feature/B until the PR for feature/A merges, but a small typo can make that fail silently.
It would be nice if there was an obvious user-facing confirmation that Depends-On: was parsed successfully. One option would be to post a comment, like the existing "Mergify rebased successfully" comment. Another option would be an emoji on the PR description, like what is done when commenting "@mergifyio rebase".
Actual Behavior
depends-on: #1234, depends on: #1234, Depends-On #1234 etc don't create a dependency, but look correct at first glance.
Steps to Reproduce the Problem
- Create two PRs
- Add
Depends-On: #1to PR#2, but get the syntax wrong - Approve PR
#2and watch it merge automatically
Specifications
- Pull Request URL:
- Mergify Config URL:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the Depends-On: #1234 syntax is parsed and compare it with the existing “Mergify rebased successfully” comment and @mergifyio rebase emoji behavior. Done means a visibly user-facing confirmation appears when a dependency is parsed successfully, while malformed variants do not silently pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100