Skip to content

palashmon/learn-commitizen

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Learn Commitizen Basics

npm version

semantic-release Commitizen friendly MIT License

This is sample repo for learning more about Commitizen for practice.

Main focus:

  • Semantic Release
  • Commitizen
  • cz-conventional-changelog

Steps

  1. Make new changes to repo (add/edit any file).
  2. Add the changes next for staging:
    git add .
  3. Run the following command and follow the Commitizen steps:
    npm run commit
    Commitizen
  4. Finally
    git push

Default Commit Message Format

Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject (full explanation):

<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>

Contributing

Pull requests are always welcome.
Feel free to fork and do as many commits as you want for practice.

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request

License

MIT © Palash Mondal