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,456,628
Community Members
 
Community Events
176
Community Groups

expected committer email and expected committer name name are wrong

Edited

Hi Team,

Getting error in source tree while pushing. 

Error - 

expected committer email 

expected committer name

Are wrong data going on server.

 

Please look this issue and revert as soon as possible.

 

remote: 

remote:   (c).-.(c)    (c).-.(c)    (c).-.(c)    (c).-.(c)    (c).-.(c)         

remote:    / ._. \      / ._. \      / ._. \      / ._. \      / ._. \         

remote:  __\( Y )/__  __\( Y )/__  __\( Y )/__  __\( Y )/__  __\( Y )/__        

remote: (_.-/'-'\-._)(_.-/'-'\-._)(_.-/'-'\-._)(_.-/'-'\-._)(_.-/'-'\-._)        

remote:    || E ||      || R ||      || R ||      || O ||      || R ||        

remote:  _.' `-' '._  _.' `-' '._  _.' `-' '._  _.' `-' '._  _.' `-' '.        

remote: (.-./`-'\.-.)(.-./`-`\.-.)(.-./`-`\.-.)(.-./`-'\.-.)(.-./`-`\.-.) 

 

Regards

Himanshu 

3 answers

 

That's from the Yet Another Commit Checker add-on.  One of its options is checking to make sure the AUTHOR and COMMITTER metadata in the commit objects you're pushing match the name and email-address configured for you on the Bitbucket server.

If you do a "git log --pretty=fuller @{u}..HEAD" it will probably show you the problem.   Here's what that command shows for me:

 

commit 115a14ccad19351ede7ded8d708aeab83263ee1c
Author: G. Sylvie Davies <sylvie@bit-booster.com>
AuthorDate: Tue Oct 31 00:22:35 2017 -0700
Commit: G. Sylvie Davies <sylvie@bit-booster.com>
CommitDate: Tue Oct 31 00:22:35 2017 -0700

In my case my name "G. Sylvie Davies" and my email address "sylvie@bit-booster.com" do match the values on my Bitbucket Server user profile.

To change these values on your local git environment:

git config --global user.name  "Mona Lisa"
git config --global user.email "mona.lisa@gmail.com"

 But that only changes the data for new commits.  Old commits are immutable.  You need to regenerate the commits you are trying to push to take in the updated metadata.  This should do the trick:

git commit --amend --reset-author

Try pushing again after that's been done.

Even above not working for me. 

Like Baruch Atta likes this

These commands do not work for me

git config --global user.name  "Mona Lisa"
git config --global user.email "mona.lisa@gmail.com"

Even when I set the global user name to the one that is "expected" it still uses the original unexpected name.

Is there a way to just wipe the whole thing away and start over?

I faced same issue with name while trying to push code.

updated the name as in bit bucket using command

git config --global  user.name <<here enter ur bit bukcet name>>

As the name is changed, we have to update the commit also using amend

 

git commit --amend -m 'add message'

Thank you . it worked for me.

I had the same error. It happened when I tried to push while the remote branch was deleted by someone else. I have solved it as follows:

  1. checkout any other branch (otherwise you can't do step 2)
  2. delete the local branch on which the push failed
  3. fetch with option 'Prune tracking branches not present on remote(s)' 
  4. create the remote branch
  5. checkout the remote branch
  6. redo changes and commit them
  7. push

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events