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.
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".
Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster ! While we’re all excited about the new improvements to Bitbucket ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events