GIT Error:- expected committer email '' but found 'karan@xyz.com'

Question

Git push is getting rejected with the following error message:

expected committer email '' but found 'karan@xyz.com'

I have already tried:

1. setting use properties in .gitconfig file.
2. trying git push making different clones of same repository.
3. setting up whole system all together after formatting it.

But none has worked. What else can I do to resolve it.

Answer 1

This worked for me

git config --global user.name "Correct Name" 
git config --global user.email name@email.com 
git commit --amend --reset-author

Answer 2

This work for me:

git config --global user.name "Correct Name" 
git config --global user.email name@email.com 
git commit --amend --reset-author

It will show the screen where you can edit the commit message, after edit or keep it as it is, then press escape and then :wq and hit enter.

Then:

git push

Answer 3

This doesn't seem like a git limitation, but should be some kind of pre-receive hook on the remote side (the Git repository hosting service/server to which you are pushing to)

That hook seems to parse the commits and check the committer email against a specific criteria which rejects karan@xyz.com.
You should check with the remote side administrator to see what is going on.

---

The OP Karan Singla confirms in the comments it was an issue at the server side:

Issue got resolved. Admin re-created my account and it is working fine now.

Answer 4

Had a similar situation where a server side hook was involved, as @VonC mentioned, while trying to do the initial push to a empty Bitbucket Git repo (self-hosted in-house Bitbucket instance). The push contained commits from me and other earlier colleagues.

In my case it was the YACC (Yet Another Commit Checker) hook which complained about some e-mail addresses not known in the server. Those e-mail addresses were used in commits during early project setup, by colleagues who meanwhile left the organization, an their accounts were deleted. See also this Atlassian article.

But, instead of globally deactivating the hook (as suggested by the Atlassian article), I :

• have first explicitly activated the hook for my repo with empty settings (that overrides for my repo the global hook settings),
• then made the initial push,
• and then disabled again the plugin for my repo (plugin remains active, but only with the server-wide hook settings!).

Answer 5

git config --list --show-origin

Allows you to see the file where the setting is coming from. In my case it was an unrelated git settings file somehow making it into my portable git install.

Answer 6

I would suggest to open git terminal and set correct email. This worked for me when I encountered same issue.

git config --global user.email "your_correct_email@example.com"