feat: enforce Conventional Commit style commit messages #282
+1,805
−801
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
defunctzombie
approved these changes
Jun 22, 2018
broofa
added a commit
that referenced
this pull request
Jun 22, 2018
* feat: enforce Conventional Commit style * chore: drop node@0.12 from Travis tests
This was referenced Oct 27, 2024
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.
Adds pre-commit check to insure commit messages conform to https://conventionalcommits.org/ .
This is necessary (or at least desirable) to insure the impact of every commit is reflected in the semver and CHANGELOG docs when
standard-versioncommand is run.Note: 'Dropped support for node@0.12 in Travis tests due to typicode/husky#308 . We can add 0.12 test support back in if/when that bug is fixed, or it becomes a real issue, but it was EOL'ed almost two years ago. I'm okay telling anyone who cares to pin their
uuidversion to a prior release and go from there.