feat: support commit-analyzer presets #227
Open
Conversation
This file contains hidden or 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
* `feat`: support different commit-analyzer presets ## purpose * adding support for `conventionalcommits` (this doesn't preclude the other presets, but this is the one specifically that i am after) ## caveats * this does not support the `presetConfig`, meaning we can only provide the most basic implementation [full list of supported presets](https://github.com/semantic-release/commit-analyzer?tab=readme-ov-file#options)
|
Oh – this is really nice! It’s a much better solution than #209, since this won’t by default change existing behaviour. @mathieudutour what do you think? Would you consider merging this? |
|
This would be great for us as well! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
feat: support different commit-analyzer presetspurpose
conventionalcommitsthis doesn't preclude the other presets, but this is the one specifically that i am after
caveats
presetConfigoption, meaning we can only provide the most basic implementation. this is also the case forangular, which has been the default up to this pointfull list of supported presets
closes #226
closes #208
closes #80