When creating a repository, the default values for the Pull Requests settings "Require n approvers" and "Requires a minimum of n successful builds" are that both are disabled (so no approvers nor successful builds are required) and the grayed-out value for n for both is 1 (so if I did check the boxes, they would be set to 1). Is there a way to change the default values for these at either the project (ideal) or whole Stash instance (less ideal) level? We would like to have new repositories automatically set upon creation to require 2 approvers and 1 successful build to allow a pull request.
This is exactly what our new add-on Repository Templates for Stash provides. Beside many other things it is able to provide defaults for (branch and repository permissions, branch model, hook settings, etc.), it can also set default pull request settings on a project level.
Hope this helps.
We are looking as well for a possibility.to adjust settings of existing repositories (not new ones whereas the template approach is not working for us).
Even though there might be a possibility like pointed out in https://answers.atlassian.com/questions/268889 and we are able to adjust nearly all kind of settings, the settings on the PullRequest-level stay opaque.
Anyone got any ideas how to access these settings?
With the upcoming release 1.1 of Repository Templates for Stash (shipped in the next few days), we will also provide synchronization of settings between the template and its associated repositories. Are you looking for a way to reset the settings of repositories according to its master (or template) or do you just want to have new settings (e.g., when a branch permission is added) replicated to the associated repositories?
We have a bunch of existing repositorys and we want to ensure (with the help of a scheduled jenkins-job and the Stash REST API) that all repositories got the same settings (even if by any fault, someone changes any setting. These settings should be then overwritten automatically).
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot