PedroJesusRomeroOrtega/semantic-commit

To test Conventional commits and nxg-semantic-version

SemanticCommit

This project was generated with Angular CLI version 9.1.3.

I used to test Commitizen, Husky, Commitlint, Conventional changelog and Conventional Commits to generate automatically a Changelog file and better git history

Steps

1. Ensure you have python installed.
2. Install Commitizen locally
3. Add commit script to package.json:

   "scripts": {
    "cm": "git-cz"
   }
   

4. Install Visual Studio Code Commitizen extension
5. Install Angular CommitLint
6. Install Husky to allow git hook with Commitlint
7. Use Angular Convention
8. Install Standard-version
9. First release for Changelog use npm run release -- --first-release and the following releases npm run release
10. You can try npm run release -- --dry-run to look what is going to happen

Squash your commits before doing pullrequest or genereating new releases

References

• Enhance your git log with conventional commits
• Git Tools - Rewriting History
• Git: Squash your latest commits into one
• Conventional commits
• Angular commit message guidelines
• Release management in Angular with Lerna
• nxg-semantic-version

Disclaimer

For the first three commits I should have use chore type instead of feat

Development server

Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Code scaffolding

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.

Build

Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.

Running unit tests

Run ng test to execute the unit tests via Karma.

Running end-to-end tests

Run ng e2e to execute the end-to-end tests via Protractor.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.