Learn Commitizen Basics

![npm version](http://npm.im/learn-commitizen)
![Greenkeeper badge](https://greenkeeper.io/)
![semantic-release](https://github.com/semantic-release/semantic-release)
![Commitizen friendly](http://commitizen.github.io/cz-cli/)
![MIT License](http://opensource.org/licenses/MIT)

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:
``bash git add .`3. Run the following command and follow the Commitizen steps:`bash npm run commit`!Commitizen 4. Finally`bash 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):

`():


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-feature3. 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