We have a Stash Project with ~30 repositories, each containing one submodule. The root-repo (the one holding the git submodule configuration) is also contained in the project. During development we almost always need to change code in more than one module, so we have to create pullrequests in each submodule separately, even if they belong to the same ticket/changerequest/userstory/bugfix.
So, is it possible to create one pull request for changes in multiple repositories?
We have a similar situation with pull requests and submodules. Even without the submodule aspect there may be situations where a global project change may require that the repositories are updated in a specific sequence. For example for repository B should be merged then repository A should be merged, etc. Being able to put conditions on a pull request merge might address the OP requirement. If one could say, pull request A can't be approved and merged until pull B is approved and merged that would at least prevent an out of order issue. It doesn't address the OP desire to create a single pull request but it means that multiple pull requests are completely independent which might minimize the issue of creating multiple requests.
i dont think thats possible, because pull-request merges create always a new commit.
And those new commits in the submodules are not the those you have linked in the "parent" pull-request's commit.
In other words: You need to merge the commits in the submodules first before you can even link them in the parent repository.
Nonetheless, it might be beneficial for your scenario if Stash could group several independend pull-requests into one user action.
I think hierarchially linked pull requests are the answer. The pull request is defined based on branches, not commits. Child just needs merged transition to trigger parent Pull Request.
For reviewer it should still be ok, because they are looking at the diff introduced by the software change.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot