Skip to content

Oleg-Kolosov/Requirements-for-Commit-Names

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

8 Commits
Β 
Β 

Repository files navigation

This specification is based and modified on the AngularJS commit message convention.

Commit Message

 init   (hw_3):    add solutions for tasks
<type> (<scope>):  <short summary>
  β”‚       β”‚             β”‚
  β”‚       β”‚             └─⫸ Summary in present tense. Not capitalized. No period at the end.
  β”‚       β”‚
  β”‚       └─⫸ Commit Scope: hw_1|hw_2|hw_3|hw_4|hw_5
  β”‚
  └─⫸ Commit Type: build|docs|feat|fix|perf|refactor|test|init

Type

Must be one of the following:

  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • docs: Documentation only changes
  • feat: A new feature
  • fix: A bug fix
  • perf: A code change that improves performance
  • refactor: A code change that neither fixes a bug nor adds a feature
  • test: Adding missing tests or correcting existing tests
  • init: start project/task

Examples

  init(hw_1): add solutions for tasks

  refactor(hw_5): rename variables 

  feat(hw_7): add solution for advanced level task 1-4

  fix(hw_3): fix bug in task 3

  docs(hw_12): add technology list

watch original

About

Example of organazing commit names πŸ“œ

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published