Pulling to the master branch requires a completed Change Request Script Merge Checks – Require commits to be associated with a Jira issue Bitbucket Settings
The master branch is always working toward the next release and is the basis for that release’s branch
Therefore, changes to the master branch are strictly controlled
Proper authorization, via a completed change request, is required
Hook Type Require commits to be associated with a Jira issue
Note Require a valid completed change request when merging to the master branch.
Condition mergeRequest.pullRequest.toRef.id.matches("refs/heads/master")
JQL clause template (issueType in ("Change Request", "CR Sub-task"))
AND (status = "Completed")
Thanks for any help
Hey I know we talked outside of this channel, but for posterity:
The solution here was this wasn't actually intended to be a pre-receive hook, but a merge check.
"mergeRequest" was undeclared because a pre-receive hook could be any type of push, not just a merge. So the merge check is where you would be able to use the "mergeRequest".
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.