You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi everyone! I'm currently using Semantic Release in my project and I'd like to configure it so that it doesn't trigger a release for commits labeled as fix or feat. However, I couldn't find a straightforward way to achieve this in the existing configuration options.
I propose adding a feature or configuration option that allows users to exclude specific commit types, by setting a certain prefix to false. I found an example for scopes.
As you can see, now I set those default prefixes to prerelease and that's not what I am aiming for.
If this feature exists, please, let me know how to achieve it.
Thanks in advance!
The text was updated successfully, but these errors were encountered:
You can also do this "commits that contains '[skip release]' or '[release skip]' in their message will be excluded from the commit analysis" @Menosc although not as convenient.
You can also do this "commits that contains '[skip release]' or '[release skip]' in their message will be excluded from the commit analysis" @Menosc although not as convenient.
Another thing I do to skip a release is just not use Angular commit convention and the commit is ignored.
@travi@hobbitronics thank you guys! I chose [skip release] as a quick fix for now. I do appreciate your answers. You helped a lot. I felt the lack of this information in the official documentation. Is it worth adding it there? If yes, I can do that.
Hi everyone! I'm currently using Semantic Release in my project and I'd like to configure it so that it doesn't trigger a release for commits labeled as
fix
orfeat
. However, I couldn't find a straightforward way to achieve this in the existing configuration options.I propose adding a feature or configuration option that allows users to exclude specific commit types, by setting a certain prefix to
false
. I found an example for scopes.Here is an example of my package.json file:
As you can see, now I set those default prefixes to
prerelease
and that's not what I am aiming for.If this feature exists, please, let me know how to achieve it.
Thanks in advance!
The text was updated successfully, but these errors were encountered: