How to commit no change and new message?

by

There’s rarely a good reason to do this, but the parameter is --allow-empty for empty commits (no files changed), in contrast to --allow-empty-message for empty commit messages. You can also read more by typing git help commit or visiting the online documentation.

While the tree object (which has a hash of its own) will be identical, the commit will actually have a different hash, because it will presumably have a different timestamp and message, and will definitely have a different parent commit. All three of those factors are integrated into git‘s object hash algorithm.

There are a few reasons you might want an empty commit (incorporating some of the comments):

  • As a “declarative commit”, to add narration or documentation (via DavidNeiss) including after-the-fact data about passing tests or lint (via Robert Balicki).
  • To test git commands without generating arbitrary changes (via Vaelus).
  • To re-create a deleted bare repository using gitolite (via Tatsh).
  • To arbitrarily create a new commit, such as for re-triggering build tooling (via mattLummus) or for the sake of personal logging or metrics (via DynamiteReed). However, think twice: depending on your branch/merge structure, commits may live for a very long time, so a “just commit nothing” strategy may be inadvertently pollute your team’s repository with temporary workflow artifacts and make it hard to separate code revisions from ephemeral cruft.

Other strategies to add metadata to a commit tree include:

  • Separate branches or lightweight tags that always point to a commit of a particular status (e.g. “last accepted commit” or “current staging commit”).
  • Annotated Tags for a way to record timestamp, committer, and message, pointing to an existing commit without adding an entry in the commit tree itself.
  • git notes to associate a mutable note on top of an existing immutable commit.

More Related Contents:

  1. How to revert multiple git commits?
  2. How to remove selected commit log entries from a Git repository while keeping their changes?
  3. How to configure Git post commit hook
  4. Updates were rejected because the remote contains work that you do not have locally
  5. How can I revert multiple Git commits?
  6. How can I push a specific commit to a remote, and not previous commits?
  7. Remove specific commit
  8. Start a Git commit message with a hashmark (#)
  9. Changing git commit message after push (given that no one pulled from remote)
  10. Git: How to ignore fast forward and revert origin [branch] to earlier commit?
  11. How to list all commits that changed a specific file?
  12. How to undo “git commit –amend” done instead of “git commit”
  13. How can I view prior commits with git blame?
  14. How to commit my current changes to a different branch in Git [duplicate]
  15. Install specific git commit with pip
  16. Why Git is not allowing me to commit even after configuration?
  17. git commit frequency
  18. Git: How can I find a commit that most closely matches a directory?
  19. Can you change a file content during git commit?
  20. Error “Updates were rejected because the remote contains work that you do not have locally”
  21. How do I create a new Git branch from an old commit? [duplicate]
  22. How to delete the last n commits on Github and locally?
  23. Git: add vs push vs commit
  24. git find fat commit
  25. How do we verify commit messages for a push?
  26. Git: Merge a Commit into a different Branch
  27. Editing the git commit message in GitHub
  28. GIT commit as different user without email / or only email
  29. Git commit with no commit message
  30. Git commit to common submodule (master branch)

Leave a Comment