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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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,409,240
Community Members
 
Community Events
169
Community Groups

Is there a way to disable commits from unknown users on a private repository?

I'm seeing unknown users checking in code to PRIVATE repositories. I found out who they are by reviewing it with my teams, but the system should automatically disallow this from happening. If a repository is PRIVATE, it should ONLY allow access to the people that have permissions to access it. That includes doing any management on it.

1 answer

1 accepted

0 votes
Answer accepted
jyo Atlassian Team Aug 14, 2017

Hi there,

 

The issue here is that people who currently have access to this repository are committing with incorrect e-mail aliases. See: https://confluence.atlassian.com/bitbucket/set-your-username-for-bitbucket-cloud-actions-272597445.html

If they have an unknown e-mail set in their .gitconfig file, then it will show up as "Unknown" under Bitbucket, as it does not match their primary e-mail on Bitbucket. Once they fix this, their subsequent commits will show up under their correct user account.

They can also set their Email alias under *Bitbucket Settings*, so it can attribute to incorrect commits to the correct user.

There is no way to disallow this from happening, but I've created a feature request: https://bitbucket.org/site/master/issues/14663/create-flag-to-prevent-unknown-committers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events