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: #1 to PR #2, but get the syntax wrong
- Approve PR
#2 and watch it merge automatically
Specifications
- Pull Request URL:
- Mergify Config URL:
Expected Behavior
Sometimes the changes for
feature/Bdepend on the changes forfeature/A. TheDepends-On: #1234syntax allows me to block mergingfeature/Buntil the PR forfeature/Amerges, 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 #1234etc don't create a dependency, but look correct at first glance.Steps to Reproduce the Problem
Depends-On: #1to PR#2, but get the syntax wrong#2and watch it merge automaticallySpecifications