When to use “chore” as type of commit message?
Can anyone provide a couple of examples of its use?
Another maybe not related question: What’s the proper type of messages of commits for modifying files like
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 “
git chore "commit-message-here" -> git commit -m 'chore: commit-message-here'
.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
- private internal methods…
Although Owen S mentions in the comments:
Looking at the Karma page you link to, I suspect that
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.)