When to use “chore” as type of commit message?

What is the use of chore in semantic version control commit messages? Other types like feat or fix are clear, but I don’t know when to use “chore”.

Can anyone provide a couple of examples of its use?

  • Tagging commit messages and changesets
  • How do I make Git use the editor of my choice for commits?
  • Does Git allow me to write my next commit message gradually during developing?
  • How to edit incorrect commit message in Mercurial?
  • Git: change HEAD commit's message without touching the index
  • Suggestions for a good commit message: format/guideline?
  • Another maybe not related question: What’s the proper type of messages of commits for modifying files like .gitignore?

  • TFS/Git extensions seems to ignore .gitignore
  • Best solution for “No Scheme” issue in Xcode 4 after defected merging git branches
  • How can I upload committed changes to my GitHub repository?
  • Why does Gerrit not include the change-id into merge commits?
  • SmartGit won't authenticate with ssh
  • git submodule and “no branch”
  • One Solution collect form web for “When to use “chore” as type of commit message?”

    You can see a short definition in “Git Commit Msg”:

    chore: updating grunt tasks etc; no production code change

    It is used in:

    • “Semantic Commit Messages” and in
    • the project “fteem/git-semantic-commits“.

       git chore "commit-message-here" -> git commit -m 'chore: commit-message-here' 

    Modifying the .gitignore would be part of the “chores”.

    grunt task” means nothing that an external user would see:

    • implementation (of an existing feature, which doesn’t involve a fix),
    • configuration (like the .gitignore or .gitattributes),
    • private internal methods…

    Although Owen S mentions in the comments:

    Looking at the Karma page you link to, I suspect that grunt task may refer specifically to Javascript’s build tool grunt.
    In which case, they probably didn’t have in mind changes involving implementation or private internal methods, but rather tool changes, configuration changes, and changes to things that do not actually go into production at all.
    (Our shop currently uses it for those, and also for simple refactoring.)

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