During merge request if specific file <PROD PROP> have changes, it should allow merge after specific person/team approvals other wise it stop to merge.
Need help to make custom script for above request.
Hi @maheswarreddyt ,
If you are using ScriptRunner for Bitbucket I would suggest you look a the following Built-In Scripts that should help you achieve what you want to do.
To start with you can block a merge using a Conditional Merge Check. Here is the documentation:
As you can see in the example, the merge is blocked if any of the participants state the PR needs more work. You can amend this example for your needs. For example, blocking the merge when a particular reviewer has not yet approved the PR.
You can also use ScriptRunner for Bitbucket to add mandatory reviewers to Pull Requests. This can be done in a couple of ways.
1. As a simple list of users or groups you can use the Auto-Add Reviewers to a Pull Request Built-In Script:
2. Or, if you have more complex requirements, for example adding mandatory reviewers based on a particular file change etc, you can use the more advanced Dynamically Add Reviewers to a Pull Request Built-In Script:
Please let me know how you get on using these ScriptRunner for Bitbucket Scripts?
Product Manager, ScriptRunner for Bitbucket
that's an interesting scenario, in fact it is quite common. While I can't supply a script that does exactly what you need, your requirement consists of 2 basic steps,
1. If a certain file path is part of a pull request changeset, add a mandatory reviewer.
2. Before the pull request can be merged, the mandatory reviewer must approve, otherwise the PR is blocked.
We have built out this functionality (no coding required) as part of the Workzone for Bitbucket (Server/Datacenter) app.
If you are on a server or Datacenter instance, please let me know if need any help to set this up. Here is a start .
There are also other apps like Scriptrunner available that can potentially solve the problem.
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
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