Merge Request dependencies
Problem to solve
When working on a merge request, it may depend on work being done in a different merge request. Rather than depending on tests failing to block the merge, there should be an explicit way to document the dependencies.
For example, a feature might be implemented over multiple merge requests: backend with feature flag, frontend, documentation, remove feature flag.
Further details
A change, even very small changes, may require changes by multiple people to different parts of a project. It is possible to group these into a single branch, but this can be frustrating when each aspect of the change is relatively isolated despite being dependent.
For example, writing the documentation depends on the implementation being complete and matching the design, but the implementation details of the feature won't impact the documentation. Handling the two changes in separate merge requests may be more convenient.
Proposal
When editing a merge request, I will be able to add a Merge Request Dependency
If the merge request a dependency has not merged, the dependent merge request will be blocked from being merged.
