Define a commit message format
Description:
Set a common format, how to write commit message. State some examples. Optionally, define a list of "commit message tag" ([BUGFIX], [FEATURE], etc.) and explain their usage.
Links:
https://gist.github.com/robertpainsi/b632364184e70900af4ab688decf6f53
https://wiki.openstack.org/wiki/GitCommitMessages#Information_in_commit_messages
https://docs.typo3.org/m/typo3/guide-contributionworkflow/main/en-us/Appendix/CommitMessage.html
Keywords:
version control, git, commit message
Motivation:
Defining commit message format can provide better orientation in single commits and minimal context of change made by the commit.
Requirements/Prerequisities:
version control, git
Level:
activity: description what you have to do in your specific level (e.g. define interface)
Application domain:
Software engineering
Main phase:
Development: Implementation/Code/Build
Related literature:
Conventional Commits. (n.d.). https://www.conventionalcommits.org/en/v1.0.0/
In which projects do/did you use this practice?
https://onemocneni-aktualne.mzcr.cz/
Full-stack Developer
3–5 years of experiences
Masaryk University
| 1. How do you rate the potential benefit for your projects? | 2 |
| 2. How often are you using that practice? | 5 |
| 3. What is the effort to introduce the practice in your project upfront? | 1 |
| 4. What is the effort to apply the best practice in your project daily basis? | 1 |
Questions 1, 3 and 4 (1 = Low, 5 = High)
Question 2 (1 = Never, 5 = Always)