What is the difference between author and committer in Git?

I just came across the following commit on GitHub:
https://github.com/felixge/node-formidable/commit/0a0b150668daa3c6f01626d2565b898e5da12392

How does one go about having multiple authors on the same commit like that?

  • Changes which are not yet merged to remote
  • Do I need to checkout and pull a remote git branch before I merge it in?
  • How to get git branch/tag names in CMake, from external project?
  • Can't create new branch.Unknown protocol
  • Permanently disable commit message requirement in Sourcetree
  • Definitive recommendation for git autocrlf settings
  • ruby markdown parser with WikiWord support?
  • git rebase - difference between rebasing against develop and origin/develop?
  • finding out the last modified time of all modified files in git
  • Problems making a .gitignore in a “main” module affect a submodule properly
  • What's wrong with using https in a git repo?
  • Git command to find what branches were merged into current branch and when
  • 3 Solutions collect form web for “What is the difference between author and committer in Git?”

    That’s not really two authors – that’s an author and a committer. The two fields have different meanings. The author is the one who created the content, and the committer is the one who committed it. When you do a normal commit, you are both. (And both come with an associated email and timestamp.) But they can become different in a few key ways:

    • git format-patch/git am – this pair lets you turn commits into patches, generally submitted by email, then have someone else apply them. You remain the author; the person who applies them is the committer. This is pretty definitely what happened on github there.

    • git commit --amend, git rebase, git filter-branch. These are all basically variants on history rewriting, ranging from single commit to some history of a branch to the entire history. They can potentially modify the comitter information – in particular, they always rewrite the committer timestamp. The original author remains in place (in default modes of operation), and if the author is also the one doing the rewriting, their name and email stay, but the timestamp is naturally different.

    There aren’t multiple authors associated with that commit (nor is it currently possible to assign multiple authors to a single commit). In this case, gliese1337 was the author, and felixge was the committer. Most likely, this occurred because gliese1337 submitted a pull request which was accepted and then committed by felixhe (the repository owner). That workflow’s pretty common on GitHub. This is also helpful for instances when a project maintainer receives a patch via email, so the author of the patch itself still receives credit for the patch, even if he or she doesn’t have commit access to the project.

    A couple of related links:

    Short Git Wiki section on author attribution
    A feature request for multiple author functionality in Git core

    It is not multiple authors. One is the author and another is commiter.

    If you’d make a clone you could see it clearly:

    $ git cat-file -p 0a0b150668daa3c6f016
    tree 91edcb411b7cd0708c1f5bb05621846146c9425a
    parent 6b9ffe3653fe59f035b01ba1f46b5f2650be00ca
    author Logan Kearsley <chronosurfer@gmail.com> 1308937685 -0700
    committer Felix Geisendo╠Иrfer <felix@debuggable.com> 1309117893 +0200
    
    Slight but definite & consistent performance boost.
    
    Git Baby is a git and github fan, let's start git clone.