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
No, I'm not squashed. I'm testing on single commits only for now.
Forcing a commit message in some format is definitely a problem to look on for me. Until I don't have that, DEFAULT_BUMP = patch would be fine for me, I already know how to do it.
Yes the last message in history should take precedence if there are multiple commits.
First of all, I love this workflow, it works really good.
I have above code in my version.yml file.
I wanted to follow semantic versioning rules to bump version.
For e.g
If my message says
fix: some message
orfix(some scope): some message
then it should trigger a patch version bump
If my message says
feat: some message
orfeat(some scope): some message
then it should trigger a minor version bump
Any idea how to configure it?
The text was updated successfully, but these errors were encountered: