Update: Support conventional commits #55
Merged
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
aladdin-add
reviewed
Apr 28, 2021
|
Fixed linting errors. |
aladdin-add
reviewed
Apr 29, 2021
btmills
reviewed
Apr 29, 2021
btmills
previously approved these changes
Apr 30, 2021
aladdin-add
previously approved these changes
Apr 30, 2021
|
a conflict needs to be fixed. |
|
Conflicts resolved. |
btmills
approved these changes
May 1, 2021
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.
This change allows eslint-release to interpret conventional commit-style commit messages to generate the correct release information. This will allow us to transition from our own commit message style into conventional commits without disrupting our releases.
Note: Conventional commits uses "feat" to be equivalent to both "New" and "Update" for us. For simplicity, I decided to map "feat" to "New".