inter-module dependencies for merge-requests
If submitting a merge-request that requires a certain feature from an other module, which is not yet merged, our ci-tools currently support some heuristic to switch in all modules to the branch name of the MR, if this branch exists. Otherwise master is used (if I understood everything correctly).
It would be nice if we could make this behaviour more flexible.
- it would be nice if the heuristics follow the branch graph, so that an MR for a release branch uses the corresponding release branches of the other modules (perhaps this already works somehow?!)
- it would be helpful if we could add somewhere some meta-data to the MR, which might then include hints on which branches to use for the dependencies.