git-commit-message

Is there a similar template, but for conventional commits[1]? [1] https://www.conventionalcommits.org/en/v1.0.0/ EDIT: We reject the git commit message style of projects such as Angular, Commitizen defaults, etc. - Because these use a leading tag that is sometimes a word, sometimes an abbreviation, sometimes a plural noun, etc. - Examples are using "feat" for feature, "docs" for document, "perf" for performance improvement, etc. - Instead we use "Add" for adding a feature, "Document" for documenting help, "Optimize" for performance improvement, etc. - Active verbs are easier to skim, and easier to use for people from other cultures who may be less-comfortable using English. and We reject using a ticket id number in the summary line. - Instead, we use fully-qualified URLs in the commit message body. - This is because many of our projects u

Write meaningful git commit messages, always. Even in stupid side projects that don't matter. Because then when you're at work, it will be second nature to write good messages, and your colleagues will absolutely appreciate it. I've been following the keywords here: https://github.com/joelparkerhenderson/git_commit_message

Each team is free to choose their own way. Personally I like topic branch names that are read like a present tense imperative commit messages e.g. add_feature_for_user_to_like_a_post, fix_relation_between_a user_and_a_post, optimize_search_speed_for_a_user_to_see_posts. The names are long and meaningful. Autocompletion makes these work well. Our git commit message conventions are: https://github.com/joelparkerhenderson/git_commit_message To store info about metadata, such as task board number, we edit the branch description, and enable the description to go into the merge message. A good short intro to branch descriptions: https://ericjmritz.wordpress.com/2015/11/13/using-branch-des...

Git commit message: https://github.com/joelparkerhenderson/git_commit_message How to write better git commit messages, as a repo README. For example, we use wording Add/Fix/Optimize/Refactor and semantic versioning, etc. Git commit template: https://github.com/joelparkerhenderson/git_commit_template/b... You can use a template to improve git commit messages, that prompts for writing "Why" you are making a change, and any co-authors, and any links, etc. Constructive advice welcome. I'm the author.

How to write a great git commit message: http://github.com/joelparkerhenderson/git_commit_message

If you like this format, then you may want to try a similar format that uses the same purpose, plus uses words that easier to read and that make more sense to people in more cultures. We use Add, Fix, Refactor, Reformat, Optimize, etc. See my comment on this thread or https://github.com/joelparkerhenderson/git_commit_message

Feedback on this git commit message convention is welcome, and so are pull requests: https://github.com/joelparkerhenderson/git_commit_message