Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,301,209
Community Members
 
Community Events
165
Community Groups

Allow merge to master or modifications to master with pull request

Edited

Today I work with the GitFlow method available from GitKraken.

 

When there's a new feature we start a branch on the Feature that goes to Develop and then there's a Release.

When there's a bug fix, we start a branch on the Hotfix, which goes to Develop and then a Release.

 

It happens that when there is a release, the code is placed in the Master. But since there is a risk that something was accidentally uploaded or even the developer deleted something, we want to approve everything that goes to the Master.

 

We saw this Bitbucket article "Suggest or require checks before a merge" and enabled the branching permission, but still, people are able to send everything to the master without having to approve what was sent. How can I control what goes to the Master?

 

Screenshot.png

1 answer

0 votes

Hi @ThePokyWizard,

I see that you created a support ticket for this issue, but I wanted to leave a reply here as well for any other users who may come across your post with the same question.

Selecting certain merge checks only will show a warning when someone tries to merge and the merge checks are not successful.

In order to prevent a merge when the checks fail, you will need to additionally select the option "Prevent a merge with unresolved merge checks" in that dialog, which is possible if your workspace is on the Premium plan.

Kind regards,
Theodora

@ThePokyWizard If you just need to control direct push from local to remote master just enter 'master' into the Branch permission's "select branch" input field. (It's currently set to 'main')

Obviously you can nominate exceptions for some user(s) as you have done and let the rest of the team merge to 'master' via PR only.

This should be sufficient to accomplish your goal of limiting who can push to 'master'.

Let me know how you go.

Best, Ulrich

Izymes 

// Eliminate boring from work

Like # people like this

Thanks @Ulrich Kuhnhardt _IzymesCo_ ,
I made the suggested modification by support (enable: Prevent a merge with unresolved merge checks) and also changed the branch name to master and it worked.

Like # people like this

That's good to hear, thank you for the update @ThePokyWizard!

And thank you @Ulrich Kuhnhardt _IzymesCo_ for noticing the branch name!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

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...

2,265 views 2 9
Read article

Community Events

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

Events near you