Is your feature request related to a problem?
I'm always frustrated when working on large features broken into multiple stacked PRs. It's difficult for reviewers to know the sequence of PRs and if a base PR has been merged or updated.
Describe the Solution
Create a "Stacked PRs" dependency graph that automatically links PRs if their base branches are other active feature branches, enforcing merge blocks until the parent PR is merged.
Design/UI Thoughts
A horizontal node-based graph rendered with Mermaid.js or React Flow at the bottom of the PR page, visually indicating the status (Open, Approved, Merged) of each PR in the chain.
Additional Context
Useful for teams practicing trunk-based development with micro-commits.
Is your feature request related to a problem?
I'm always frustrated when working on large features broken into multiple stacked PRs. It's difficult for reviewers to know the sequence of PRs and if a base PR has been merged or updated.
Describe the Solution
Create a "Stacked PRs" dependency graph that automatically links PRs if their base branches are other active feature branches, enforcing merge blocks until the parent PR is merged.
Design/UI Thoughts
A horizontal node-based graph rendered with Mermaid.js or React Flow at the bottom of the PR page, visually indicating the status (Open, Approved, Merged) of each PR in the chain.
Additional Context
Useful for teams practicing trunk-based development with micro-commits.