Merge pull request #43 from donhector/hector2

hector2

.releaserc.yaml

@@ -101,8 +101,8 @@ plugins:
           - BREAKING
 
   # Generate us a changelog file
-  - - "@semantic-release/changelog"
-    - changelogFile: CHANGELOG.md
+  # - - "@semantic-release/changelog"
+  #   - changelogFile: CHANGELOG.md
 
   # Commit the generated changelog file into our git repo.
   # Since we are enforcing conventional commmits in our project,
@@ -112,10 +112,10 @@ plugins:
   # so our release workflow logic can easily filter out / ignore these kind of commits.
   # In fact, since recently, Github workflows knows how to handle this logic automatically
   # See (https://github.blog/changelog/2021-02-08-github-actions-skip-pull-request-and-push-workflows-with-skip-ci/)
-  - - "@semantic-release/git"
-    - assets:
-        - CHANGELOG.md
-      message: "chore(release): update changelog to ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
+  # - - "@semantic-release/git"
+  #   - assets:
+  #       - CHANGELOG.md
+  #     message: "chore(release): update changelog to ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
 
   # Create a release in Github
   - - "@semantic-release/github"

README.md

@@ -91,10 +91,10 @@ Author Information
 [commitizen-badge]: https://img.shields.io/badge/commitizen-friendly-brightgreen.svg
 [commitizen-link]: http://commitizen.github.io/cz-cli
 
-TODO
+<!-- TODO
 ------------
 Research hook execution order: We want commitizen to run prior to molecule test
 Investigate why there was no release even with `fix:` commits
 - Looks like squash merging a PR, creates a commit with the name of the PR
   so if the PR is not named conventiaolly, semantic-release will ignore it for comuputing the release
-Research semantic pull-requests, so PR titles follow conventional commits spec
+Research semantic pull-requests, so PR titles follow conventional commits spec -->