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

Best practice to give access to external programmer without letting him modify our branches.

We have a private repository and we want an external programmer to contribute with his code to our project. 

We don't want him to accidentally mess our code so I would like to allow him to clone the repository and when he have something to push, we have to approve it before we merge it into the master. He can't merge his branch into any our branches. 


How can we do that? How do yo do that?


Deleted user Jun 14, 2018

For this, you would go to Settings -> User and Group Access, then give the external programmer READ ACCESS only. They could then clone the repo and make a 'pull request' but they could not actually merge a pull request into your codebase.

Julius Davies _bit-booster_com_
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.
Jun 14, 2018

Good advice from @[deleted] but there's one extra step:

The external developer should fork the repo first, and then clone from their fork.

p.s.  Is this for Bitbucket Cloud or Bitbucket Server?  Essentially the same mechanism for both (and I think the fork button is in the same place in the web UI and looks pretty similar), but there can be subtle differences.

Caterina Curti
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 16, 2018

Hi @futile_studio,


As suggested by @Julius Davies _bit-booster_com_ (thank you!), using a Forking Workflow is a valid option. In this case the external programmer will be working on an entirely separated repository. It will still be possible to easily merge the changes back to the original repository.


If, instead, you want to external programmer to work directly on the main repository, you can set up branch permissions to control which branches she can access. This is available for both Bitbucket Server and Cloud:

- Branch permissions - Bitbucket Server

Branch permissions - Bitbucket Cloud

This works well if the branch names follow a well defined naming convention. Usually in this case you would also set up merge checks.




Caterina - Atlassian


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events