Can I define a rule for accepting pull requests in a branch only if the commits were previously merged in a "test" branch?
For example in our organization we have a "master" branch, a "test" branch and a diffrent branch for every bugfix (let's address them with "a", "b"...).
I want to create a rule so you are not allowed to create or aprove a pull request of brances "a" or "b"... to "master" if all the commits contained in branches "a" or "b"... are not contained yet in the "test" branch. (meaning that they were not tested)
Can you help me?
It is not possible at the moment.
More precisely, your requirement is rather custom, so I think having precisely this feature is not very realistic. But! If you look at the Bitbucket roadmap, you can see a feature coming soon which will allow developers to add custom merge checks!
This is exactly what you need to implement your requirement.
See: https://www.atlassian.com/wac/roadmap/cloud/Custom-merge-checks?search=merge&p=215ad4ab-15
I'm just wondering if having 'a' and 'b' in the 'test' branch is sufficient. Shouldn't passing the test also be a requirement? How are you currently tracking and enforcing this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.