We have developed a git project providing the capability to setup Bitbucket Server/Datacenter repository configurations programmatically and under source control. This project is Open Source now and can be fetched here: https://github.com/klarna-incubator/bec

We are using it for many of our repositories.

Have a look if you are interested and star-mark it if you like it.

Regarding the main hooks you use, I believe the functionality in "Pull Request, Please" and "Reject Force Push" should both be covered by branch permissions these days (now available at project and repo level). Is there something keeping you with these hook based settings?

Years later, I have the _actual _answer as to why my users preferred Pull Request, Please. That hook plugin provides the ability to customize the notifications received when a push fails, providing more feedback to the user than the bouncer and "talk to your project admin." They included such things as what branches are protected, and how a user should contribute their PR.

Hi, 

Is there any news about this request? For our company, it is basic to have a global Webhook launched for certain events in all repositories. Otherwise, it's cumbersome and time-consuming having to configure them for each repository. 

Regards.

It is definitely becoming tiresome to apply the same settings for each new project.

• branching model
• hooks
• merge-checks
• merge-strategies

These are things that are usually common to all projects in a company.

I am also wondering about this.  We have a lot of overhead due to the inability to globally set up many repos.  Most of these requests seem to stay open for a long time then get closed out. 

Is there any actual appetite to implement this? The issue was open in 2013 some 5 years ago.

My team works with microservices, 1 repo per service, currently at ~20 services. Every new repo needs to be created and setup individually which has become a mundane task. Not only this but you cant keep the settings in sync, i.e. you decide to change a setting and then you need to replicate it across all repos. These settings really also need to be at the project level.

The other issue is with permissions. With write permissions a user cannot create a new repo in a project but they can with admin. The problem with admin is they can change the repository settings and even change the permissions of others.

My requirements are more around setting the pull request options.

Thanks all for the feedback! Just to set expectations we're going to let the project level administration soak some more while we gather more feedback in addition to what we have already and consider enhancements after some other features we have in the works.

neoscorpe, I appreciate the kind words. We do try to be responsive, especially on highly voted suggestions. However, with around 1,000 suggestions just for Bitbucket Server (and many many more in other products), we realise that people often feel unheard when replying to every suggestion becomes increasingly unscalable. We're working on better ways to provide faster, more frequent indications of a suggestion's chances of being prioritised and better communicate what people can expect.

Regarding forks, they can be disabled globally by disabling the feature entirely. Hopefully that helps a little.

This is what I would like to apply globally.

Repository settings:

• Disable forking

Hooks:

• Protect Unmerged Branch Hook
• Reject Force Push
• Verify Committer

Pull requests:

• Require all tasks to be resolved
• Require a minimum of 1 build
• Unapprove automatically on new changes
• Merge strategy

We also use a custom hook that prevents pushes to specific branches, such as master and develop (it sounds very similar to Pull Request Please). I haven't had time to play around with branch permissions, but it sounds like they would probably achieve the same result, so being able to apply branch permissions globally would be great.

One other thing that would be awesome is the ability to configure HipChat notifications at the project-level. Typically we have a team looking after a project. At the moment we have to configure each repository with the same settings to send notifications to the same room. Moving that to the project level would make it much easier to manage.

On an unrelated note, can I just say thank you rbarnes for asking for feedback here. For those of us who create issues and add comments here on JAC frequently (or even infrequently), it often feels like you're talking to a brick wall, given the complete lack of response from Atlassian on most occasions. So to actually have someone from Atlassian not only posting a comment, but also ask for feedback, it's a refreshing change.

"Pull Request, Please" and "Reject Force Push" should both be covered by branch permissions these days (now available at project and repo level). Is there something keeping you with these hook based settings?

There was some reason my users preferred Pull Requests Please, but it's been awhile. I think it was something about allowing a build user to bypass the restrictions, but branch permissions can do that too... They probably used them entirely because that's what they used before branch permissions came out. I'm now curious if anyone is actually still using them.

Project: add group access permission and public access checkbox

Repo : pull request merge strategy = ff only

Reject force push

We would utilize the hooks more if they could be globally configured.