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,467,212
Community Members
 
Community Events
177
Community Groups

Sourcetree using wrong user name and won't push due to validation error

I have a situation on my new Windows 10 laptop and haven't been able to figure it out. This all works fine on my former laptop. When I commit and push using Sourcetree 3.4.5 or 3.4.6, it clearly shows my correct user name and user email, but after the commit, I get the message below that the user name is not valid. It is somehow pulling the wrong user name from somewhere. 

I've checked everywhere. My .gitconfig is properly configured and the Settings > Advanced is set up to "Use global user settings". Everywhere I've looked, (Credentials Manager, .gitconfig, Repository Settings, CMD git config --global, etc.) shows the correct user name and user email. I can't find where it shows LOGAN anywhere.

To further test, I've backed up my repo, cloned a fresh copy, made all my coding updates, made sure user.name and user.email were still correct, committed the change, and still get the message below:

git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks push -v --tags --set-upstream origin feature/AEM-1700:feature/AEM-1700

POST git-receive-pack (3377 bytes)
remote: GUAVA Validation Error
remote: GUAVA Commit Checker
remote: PUSH FAILED
remote: Commit ID: 912efe7baacc396e256b3d97e3832c4682929cfa
remote: The User Name: LOGAN does not contain a valid UID. User Names must be of the format 'lastName, firstName (uid)' or 'uid' and the UID must be a valid ID.
remote: The email address for this user email must be in the format of: 'uid@*.company.com
and the UID in the email must match the UID of the user name.
remote: Please correct user information for User Name: "LOGAN" Email: <blogan@company.com>

remote: Powered by GUAVA-19.11.01-SNAPSHOT
Where is Sourcetree getting LOGAN from and how can I change it?

1 answer

1 accepted

0 votes
Answer accepted

So apparently there are issues with GUAVA, so it was disabled and I'm able to push commits.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events