Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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
Community Members
Community Events
Community Groups

How to disable "builds passed" in a merge check?

I want to allow my users to disable the requirement for a "build passed" for individual Pull Requests. How do I do this?

This is for pull requests that involve documentation, not executable code. For these documentation commits, it makes no sense to do a build. A build job takes a lot of time, and ties up resources that someone else on our team could use.

Users will take this action on individual PRs, not on the Branch, Repository, or Project level. I haven't been able to find the appropriate setting on the Pull Request page, or on the Repository Settings page, and I haven't found an answer (yet) in the documentation. Any pointers?

(Product details: Bitbucket Cloud, Premium plan. I am an Admin.)

1 answer

1 accepted

0 votes
Answer accepted
Erez Maadani
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 10, 2023

Hey @Ray Depew ,

You can find this setting under "Repository settings" -> "Workflow" -> "Branch restrictions" -> Click on the "Add Branch Restriction" button on the top right corner -> Choose the "Merge Settings" tab in the opened dialog.

Intuitive... ;)

However, this solution requires the user to specify the branch name or the branch type. I'm looking for a setting that will apply to the repository universally, so that users won't have to drill down into the Branch Restrictions every time they create a PR.

Patrik S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 18, 2023

Hello @Ray Depew ,

Just adding to @Erez Maadani response, I'm afraid it's not possible to bypass the merge check, but a workaround I can think of is to create a pipeline specifically for pull requests that match the documentation/* branch pattern and configure the pipeline script to just has a simple command (such as an echo) so it doesn't take much time. Then you could have your developers always use a branch named documentation/something when they need to update the documentation that does not require the normal build to be run. That pull request should just trigger the simple build which would ideally be completed in a few seconds.

Thank you, @Ray Depew !

Patrik S

Like Ray Depew likes this

@Patrik S that's a good idea for a workaround. Thank you.

Like Patrik S likes this

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events