The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Reject Force Push, Verify Committer - enabled by default

bayer_b
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 24, 2018

Hi,

is there a way to set Reject Force Push and Verify Committer by default in case of project, or repo is created in the future?

Using scheduled REST API calls(e.g. via crontab) is not an option for us.

 

Bitbucket release: 5.13.0


Thanks,

Balázs

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Aron Gombas _Midori_
Community Champion
October 28, 2018

Modern Bitbucket versions (incl. 5.13.0) inherit repo-level hook settings for any newly created repo from the project-level hook settings. In that sense, if you set the project-level settings correctly, then the repo-level defaults will work as expected.

As far as I know there is no global setting that is inherited by the project-level settings, unfortunately.  

TAGS
AUG Leaders

Atlassian Community Events