-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
parse-commit-message: Type should be exact match #164
Comments
Hey, sorry for the late response. It's not strictly a commit validation library. I built a whole suite around all that and even GitHub (Probot) Bots back then, completely freeing me of Semantic Release. That was the whole purpose - small separate components, following the Conventional Commits spec. Because we had problems with SR. What can help you with Thanks for using it. :) https://github.com/tunnckoCoreLabs/new-release (
|
Support plan
Enterprise): Community
Context
What are you trying to achieve or the steps to reproduce?
I'm using Semantic Release to release my code. I'm writing my own GitHub Action to add / remove labels from GitHub PRs so I know what kind of release merging the PR will trigger. The script gets all the commit messages and uses the
parse-commit-message
module to get the increment type.Since
fixblahblahblah
stars withfix
, thepatch
regex matches the type. Ran into this when usingFeature: something
was aminor
but it didn't do anything withSemantic Release
.What was the result you got?
'patch'
What result did you expect?
false
The text was updated successfully, but these errors were encountered: