When enabling the merge check plugin, I'm trying to run checks only for feature and bugfix branches (standard Bitbucket naming convention) but can't seem to get the regular expression to pick them up
I'm thinking something like this: (feature|bugfix)/(.*)
as we don't know what the branch is going to be called, only that it is going to start with bugfix/ or feature/
Any ideas?
It does thanks. Maybe the text that says:
"Only branches, which will match this regular expression will be handled by the hook. If a branch does not match, the hook will skip the evaluation."
Could be changed to
"Only target branches of the merge which match this regular expression will be handled by the hook. If a branch does not match, the hook will skip the evaluation."
As that is much clearer to me?
Hi,
yes the regular expression reacts on the target branch.
Does this solve your problem?
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Or does the field mean 'Target Branch' in the case of merge checks?
Either way, I found the instructions quite confusing!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In fact, if I set the field to 'develop' or empty then for a branch named 'feature/WFBO-4160-update-etailers-welcome-fullname
' the merge protection starts working. Is the description of the field wrong and it's actually which branches do you want to ignore rather than enable?
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.