Overview
Create a tool for dependency-aware pull request workflow
Prompt
In software development, we have a microservice project. Each service is on a different repo.
Let’s say there are 3 services: A, B, C
There is a scenario where the developer submits 3 PRs for each service but C depends on B and B depends on A. This means that A needs to be approved first before B and B before C
I plan on create a simple tool to aggregate this workflow. How do I call this process?
Response
What you’re describing is essentially a dependency-aware pull request workflow. In software development, this kind of process is often referred to with terms like:
- PR Dependency Management – highlighting that PRs have an order of approval based on service dependencies.
- Chained Pull Requests – emphasizing that each PR is linked in sequence, forming a chain.
- Sequential Approval Workflow – focusing on the fact that approvals must happen in a specific order.
- Dependency Graph for PRs – if you want to visualize or formalize the relationships (A → B → C).
- Orchestrated Merge Flow – if you want to stress that your tool coordinates merges across multiple repos.
If your tool is meant to aggregate and enforce this order, a clear and intuitive name could be something like “PR Orchestrator”, “Merge Sequencer”, or “Dependency-Aware Workflow Manager.”