I want to be able to update merge checks or other things based on updates to the pull-request (via hook), so my working assumption is that this requires saving some merge-request level settings. There is always PluginSettingsFactory but that's global or repository-wide and doesn't make much sense to use on a per-merge-request basis.
Use case: To veto the merge-request if it has not been approved by a list of people which is parsed out of the code committed.
I've been so far unable to find a way to persist data easily from the receive hook to the merge request check. If I could set a key on the request context that sure would be handy...
Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs