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
My workflow is to tag normal, beta, alpha, and rc releases but not development ones. I immediately set the version number to have dev in the value as soon as I create and tag a release. I do this to make clear that the current state of the code is not in a release state but in a working state. However, cz bump seems to want to tag .dev versions. It seems silly to me to tag development versions. I currently use the --files-only flag with cz bump when setting the next version to a development version. However, this is super annoying and error-prone.
Is there any way to configure cz bump to always ignore creating a tag if I bump the version to a dev version?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
My workflow is to tag normal, beta, alpha, and rc releases but not development ones. I immediately set the version number to have dev in the value as soon as I create and tag a release. I do this to make clear that the current state of the code is not in a release state but in a working state. However,
cz bumpseems to want to tag .dev versions. It seems silly to me to tag development versions. I currently use the--files-onlyflag withcz bumpwhen setting the next version to a development version. However, this is super annoying and error-prone.Is there any way to configure
cz bumpto always ignore creating a tag if I bump the version to a dev version?BetaWas this translation helpful?Give feedback.
All reactions