GIT Error:- expected committer email '' but found '[email protected]'

Question

Git push is getting rejected with the following error message:

expected committer email '' but found '[email protected]'

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.

Solution 1

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 [email protected].
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.

Solution 2

This worked for me

git config --global user.name "Correct Name" 
git config --global user.email [email protected] 
git commit --amend --reset-author

Solution 3

This work for me:

git config --global user.name "Correct Name" 
git config --global user.email [email protected] 
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

Solution 4

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.

Solution 5

Had a similar situation where a hook was involved, as @VonC mentioned, while trying to do the initial push (which contained commits from me and other colleagues) to a empty Bitbucket Git repo (self-hosted in-house Bitbucket instance). In my case it was the YACC (Yet Another Commit Checker) hook which complained, see also this Atlassian article.

But, instead of globally deactivating the hook (as suggested by the Atlassian article), I explicitly activated it for my repo with empty settings (that overrides the global hook settings for my repo), made the initial push, then again disabled the plugin in my repo (which leaves the plugin still active, but configured with the global server settings!).

View more solutions