-
Notifications
You must be signed in to change notification settings - Fork 66
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
Support !:
commit syntax for breaking changes
#26
Comments
Hello @mikeal, |
i’d like the interface to be stable and consistent. it’s not that i’m adamant that people use conventional commits, i just don’t think this will be a very maintainable project if we start allowing that level of customization. i feel the same way about configuring whether or not every commit releases or just some, the consistency is part of the interface and keeps the usage simple. there’s plenty of other projects for doing releases though, many of which are highly configurable like https://github.com/googleapis/release-please |
Okay, I'll use some other action instead. |
|
The current rules only support the old “BREAKING” message. Conventional commits added a “fix!:” and “feat!:” for signaling breaking changes. We should just parse for “!:” for a major version bump.
The text was updated successfully, but these errors were encountered: