fix: Conventional Commit for release PR #45
Merged
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
moelsayed
approved these changes
Jul 10, 2025
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.
What this PR does / why we need it:
will add the "feat: " prefix on commit message when running
task release:minorWhich issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
when calling
task release:minor, the commit message is like "release v0.1.12" which then, when merging the PR, needs to manual adapt to semantic/conventional commit message.This is a quick'n'dirty fix by adding the prefix "feat: " to the commit message, it could be adapted depending on major/minor/patch release like described in Conventional Commits Specification
My knowledge here is lacking, but probably one of you know how to quickly implement this?
Release note: