notebook/IT/Git/Commit.md
2022-11-29 18:27:16 +01:00

629 B

Commit Convention

To be more readable you can use following commit procedure

<type>[optional scope]: <description>

<body>

<footer>

Type

  • build: modify script build (MakeFile or other)
  • chore: updatating grunt task
  • ci: Continual Integration change
  • docs: documentation changes
  • feat: new feature for the user,
  • fix: bug fix for the user
  • perf: performance improvment
  • refactor: refactoring code
  • style: formatting change
  • test: test modification

Scope

Example of scope:

  • name of job
  • logger
  • init
  • runner
  • config
  • etc...

Can reference closed issue and breaking changes