Is Git's commit atomic?

An update hook can reject parts of a commit and allow others.

update() in receive_pack.c runs in a loop which then calls the update hook possibly multiple times during a commit. Each time the update hook is called, it can return failure, seemingly allowing some refs to be updated and some not updated if rejected.

Does Git’s feature of an update hook allowing possibly part of a commit to succeed and some fail mean that Git’s commit is not atomic?

Or what am I missing here? Thanks.

  • Complicated SVN spanning multiple directories
  • Why is “origin/HEAD” shown when running “git branch -r”?
  • Rstudio and version control facilities
  • Maintaining Project with Git
  • Trunk-based development release & hotfix questions
  • Recommendations for storing project documents for shared access?
  • How to hide private information in an open source project?
  • Which Windows SVN server should I use?
  • One Solution collect form web for “Is Git's commit atomic?”

    Yes commits are atomic. It is not possible to reject part of a commit.

    The update hook may be called multiple times during a single push (not
    commit) if multiple branches are being pushed at the same time. This allows
    accepting updates to some branches while rejecting updates to others, but each
    accepted update will still point to a complete commit from the pushing
    repository.

    Git Baby is a git and github fan, let's start git clone.