Feature Request: PR Dependency Management for Improved Workflow

[KJ7LNW]

Feature Request: PR Dependency Management

Description

As our project continues to grow with more contributors, managing the order of pull request merges has become increasingly challenging. Currently, there is no automated way to enforce dependencies between PRs, which can lead to merge conflicts, broken builds, or logical inconsistencies when PRs that depend on each other are merged out of order.

Mergify (https://mergify.com/pricing) offers this feature in their FREE tier. I have no affiliation with Mergify, but wanted to highlight this as an option since it addresses our needs at no cost.

Proposed Solution

Implement an automated PR dependency management system that allows contributors to explicitly define dependencies between PRs and have these dependencies automatically enforced by our CI/CD pipeline.

Implementation Details

1. Add support for dependency declaration via PR labels (e.g., depends-on:#123)
2. Create a GitHub Action workflow that validates these dependencies
3. Integrate with branch protection rules to block merges when dependencies are not satisfied

Benefits

• Prevents broken builds from merging PRs in incorrect order
• Reduces manual tracking of PR dependencies
• Improves developer experience by making dependencies explicit
• Scales well as the project and contributor base grows

Discussion Points

• Use Mergify or implement our own solution with GitHub Actions?
• What syntax for declaring dependencies?
• How to handle circular dependencies?

@mrubens - Would appreciate your thoughts on this feature as it could significantly improve our workflow management.