@Philip Hodder thanks a lot for the great article over at build-trust-in-your-deployment-workflow-with-deployment-permissions
There seems to be a new option available under "Add a branch permission" namely "Check that all dependencies are merged". I was wondering, what kind of dependencies this refers to (I could not find anything in the docs).
Thanks a lot,
Tanju
Hi Tanju,
I'm glad that you enjoyed my article!
So this is a bit awkward... š¤
I went through the documentation to try find information and also couldn't find any details. So I asked some team mates, and it turns out it was a 20% project that one of the engineers (who has now left Atlassian) had worked on. This feature was only ever shipped to Atlassians.
The general gist of the feature is that you can link Pull Requests to indicate that one PR was blocked by another, and would notify you if you tried to merge a PR without all its dependent PRs completed.
I don't think this had been reviewed by design or product management. So I don't expect it will be turned on globally.
I've updated the screenshot to not include that option.
If this sounds like an interesting feature, feel free to open a request here: https://bitbucket.org/site/master/issues/new
Thanks for catching that for me.
Phil
Hi Phil, thanks a lot for your detailed answer! We are doing a rudimentary form of dependency checking in a validation step when running in PRs, that's why that detail piqued my interest :-)
Thanks again,
Tanju
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.