Switch from SemVer PR labels to Conventional Commits #21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. Add a git commit-msg hook to validate commit messages as they are made 2. Add a GitHub workflow to validate that all commits in a PR conform to conventional commits
Do not require semver pr labels since we are switching to using conventional commits instead.
|
Code Climate has analyzed commit 6b636c5 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 100.0% (0.0% change). View more on Code Climate. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use Conventional Commits to track what types of changes are being made.
This will ensure that all commits in this project adhere to a standardized format, which will help streamline collaboration and automate release workflows.
The GitHub branching rules should be changed to require the conventional commit workflow to succeed before PRs can be merged. This ensures that all developer commits are conventional commits. The GitHub merging rules should be changed to ensure that ONLY rebase merges are allowed. This ensures that unvalidated commit messages from merge commits or sqash commits are not added to the release branch.