Take the example of branches and commit messages related to my question:
- When I work on a feature, I name my branch feat/featureName
- When I want to test something, I checkout my junk/nameOfTest branch
- When I commit, I apply 7 rules of a great commit message
All these being said, is there a pattern I could follow to write good git tag names and descriptions in a huge repo where everyone works on his own feature?
E.g. if I work on a "user groups" feature, after 10 commits where I created the basic CRUD, should I tag it with v0.1-alpha-groups and in description I should list all controls available by now?
Please give me some examples of good git tag naming and description best-practices.
You can consider using semver2 (Semantic Versioning) for the tag naming convention.
After that, you can check out "Command-line tips for effective release announcements", which have some good tips, including the release notes production:
You have a similar approach in "Very Easy Changelogs with Git":