Just no, no way. The reason is that the author and committer data are set when committing, and this usually happens locally. A git pushwill happen later to direct existing commits to the remote repository. Since commits are already made and reference the SHA1 hash, they cannot be changed during the push operation.
What you might think is due to the presence of a pre-update or update hook that prevents people from pushing back commits that they haven't created, but that can interfere with many legitimate goals. You may find that trusting your users is the only reasonable option.
source
share