-
Notifications
You must be signed in to change notification settings - Fork 34
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
[Feature] Support no-bump option #28
Comments
Thanks for the suggestion! I'm glad you find this tool useful. I assume you're using the
Notice the |
That'd be amazing! It's exactly what I'm after, yes. Would you want to do it or would you take a PR? I'm happy either way of course. |
I'd be happy to accept a PR! Thanks! |
Just to make sure we're on the same page... I don't think this requires any new command-line option (like |
@perry-mitchell - I was just looking at the code and noticed that this functionality already exists 🤦♂️ The |
@JamesMessinger Good point! I saw this as well. I’m not sure that it’s super clear however, and having it as an option would mean less work in those workflows. What’s your opinion in this regard? |
Maybe the custom item is enough for now. It's not super clear but seems to do the job. Thanks! |
@perry-mitchell - I'm currently working on a complete rewrite of version-bump-prompt. It's almost done, and it will include a "leave as-is" option in addition to the "custom" option. Expect to see it soon. |
I use this package in a lot of projects, and it's terribly convenient, but one item which is missing in my opinion is the ability to specify a no-bump option. Sometimes a deployment fails due to some network condition in one of our projects and we'd simply like to deploy the bumped version.. It'd be great if there were a flag for such an option within
version-bump-prompt
, such as--allow-no-bump
or--opt-bypass
, for example.As
version-bump-prompt
is usually always the first step for me, having such a feature would mean that I wouldn't need to add another prompt before this one.EDIT: I'd happily add this if it's something you'd be interested in.
The text was updated successfully, but these errors were encountered: