Added semantic-release configuration to package.json. With this, new semantic versions will automatically be created as part of the build process when there's a new merge to the master branch. The next version is determined based on the git commit messages which follow the Angular Git Commit Guidelines. Once this is merged into master, git tags/releases will no longer need to be manually created.
Added commitlint and husky configuration to package.json. commitlint will help ensure git commit messages follow the Angular Git Commit Guidelines, whereas husky implements a git pre-commit hook which runs commitlint. Commit messages to this repo should now follow the same pattern being used in the ux repo.
Saved commitlint and husky as dev dependencies to the project via yarn add --dev husky @commitlint/{config-conventional,cli}
Upon merge to the master branch, semantic-release will generate a CHANGELOG.md file and push it to master.
Slack notifications will be sent to the Slack #devops-notify channel upon build start/finish, along with release information (the Slack channel can be changed to something else if preferred)
package.json. With this, new semantic versions will automatically be created as part of the build process when there's a new merge to the master branch. The next version is determined based on the git commit messages which follow the Angular Git Commit Guidelines. Once this is merged into master, git tags/releases will no longer need to be manually created.package.json.commitlintwill help ensure git commit messages follow the Angular Git Commit Guidelines, whereashuskyimplements a git pre-commit hook which runscommitlint. Commit messages to this repo should now follow the same pattern being used in the ux repo.yarn add --dev husky @commitlint/{config-conventional,cli}masterbranch,semantic-releasewill generate aCHANGELOG.mdfile and push it to master.#devops-notifychannel upon build start/finish, along with release information (the Slack channel can be changed to something else if preferred)