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,556,497
Community Members
 
Community Events
184
Community Groups

Give UserA "write" access, but UserB is making commits

Hi.

I have given UserA "write" permissions on my repo hosted on BitBucket using their email address.  But now I am seeing commits by UserB who has a different email address.

When I go to "User and group access" I only see UserA.

How can this be?  This has happened on two different occasions; I am hiring one person to work on my project, but they are sub-contracting out the work to someone else (which I do not want).

Thanks.

1 answer

0 votes
Syahrul
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 23, 2022

Hi @jamiek22 

G'day.

This can happens if UserA is using git config with UserB email address locally.

UserA is authenticating using the correct original credential.

However, the local git config username (author) is using the UserB email address. So this information is sent to the Bitbucket cloud where we use the commit author to show who made the commit.

Hence, the UI shows UserB made the commit, but if we look at our logs end it should show that the one that made the commit and pushed it over is actually UserB.

You can identify this by asking UserA to run the following commands to show his local git config username and email:

git config --list

I hope this helps.

Cheers,
Syahrul

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events