ci: edit the semantic-release preset

switch to conventionalcommits preset to get better release note reports

Author: yousrasd

CICDProcess.md

@@ -1,5 +1,5 @@
 We use [semantic-release](https://github.com/semantic-release/semantic-release) and Github Actions to automatically handle the release creation. 
-We use the Angular commit convention to write commit messages that can be parsed by semantic-release.
+We use the [Conventional Commit convention](https://www.conventionalcommits.org/en/v1.0.0-beta.4/) to write commit messages that can be parsed by semantic-release.
 The semantic-release config can be viewed in the package.json under "release".
 
 To validate commit messages, we use [commitlint](https://github.com/conventional-changelog/commitlint). See commitlint.config.js for the config file.

CONTRIBUTING.md

@@ -59,7 +59,7 @@ yarn test
 
 ### Commit message convention
 
-We follow the [Angular commits specification](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines) for our commit messages:
+We follow the [Conventional Commit convention](https://www.conventionalcommits.org/en/v1.0.0-beta.4/) for our commit messages:
 
 - `fix`: bug fixes, e.g. fix crash due to deprecated method.
 - `feat`: new features, e.g. add new method to the module.
@@ -70,7 +70,7 @@ We follow the [Angular commits specification](https://github.com/angular/angular
 - `build`: changes to the build process.
 - `chore`: any chore project changes
 
-If your changes introduce any breaking changes, make sure to specify 'BREAKING CHANGE' in the footer of your commit message. Refer to [commit message format](https://github.com/angular/angular/blob/main/CONTRIBUTING.md#-commit-message-format) for more details.
+If your changes introduce any breaking changes, make sure to specify an exclamation point (!) after your commit type(scope) and  'BREAKING CHANGE' in the footer of your commit message. Refer to [Conventional Commit convention](https://www.conventionalcommits.org/en/v1.0.0-beta.4/) for more details.
 
 Some guidelines to follow when writting commit messages:
 - Commit message needs to start with a present tense verb. For example, write: 'add new component' instead of 'added new component'

package.json

@@ -233,22 +233,47 @@
               {
                 "type": "docs",
                 "hidden": false,
-                "section": "docs"
+                "section": "Documentation"
               },
               {
                 "type": "feat",
                 "hidden": false,
-                "section": "New Features"
+                "section": "Features"
               },
               {
                 "type": "fix",
-                "hidden": true,
+                "hidden": false,
                 "section": "Bug Fixes"
               },
               {
                 "type": "perf",
                 "hidden": false,
                 "section": "Performance"
+              },
+              {
+                "type": "ci",
+                "hidden": false,
+                "section": "Other"
+              },
+              {
+                "type": "chore",
+                "hidden": false,
+                "section": "Other"
+              },
+              {
+                "type": "ci",
+                "hidden": false,
+                "section": "Other"
+              },
+              {
+                "type": "revert",
+                "hidden": false,
+                "section": "Other"
+              },
+              {
+                "type": "revert",
+                "hidden": false,
+                "section": "Other"
               }
             ]
           }