Tag in Git commit summary? -


do people use tags in commit in 1 line commit summary?

are there standard tags or commonly used tags?

git has supports "tags" seems used tagging versions "v1.8.5-rc1". "tag" don't mean tag commit or branch "v1.8.5-rc1" example.

mediawiki can tag edits minor signified m, , bot edits b.

do people put tags in commit message?

example:

[trivial] add 'foo()' method 'bar' class [minor] add 'foo()' method 'bar' class [wip] add 'foo()' method 'bar' class 
  • do people use tags such this?
  • is common practice?
  • are these called tags, or these called?
  • are there standard tags?
  • are there commonly used tags?
  • what tags in common use?
  • what syntax, word enclosed in square brackets?

git commit message conventions multiple.
everything depends on want it.

i name "commit message convention" or more precisely use case "commit message labeling".

one angular convention, use "type" 1 of:

  • feat (feature)
  • fix (bug fix)
  • docs (documentation)
  • style (formatting, missing semi colons, …)
  • refactor
  • test (when adding missing tests)
  • chore (maintain)

some other use different/more types, , emoji add commit info in message.

it's define own commit message convention (or use existing one).
if want generate changelog commit messages, convention must defined , format must allow automatic parsing


as discovered, git "tag" notion totally different , way name specific commit, used releases.


btw, there bad practices in example: - "wip" notion should in branch - commit message should answer question "why?" not "what?" (the git diff give information. take @ "a note git commit messages"


Comments

Popular posts from this blog

neo4j - finding mutual friends in a cypher statement starting with three or more persons -

php - How to remove letter in front of the word laravel -

minify - Minimizing css files -