-
Notifications
You must be signed in to change notification settings - Fork 10
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
Feture Request #21
Comments
Hi Bjørn Smith, Thanks for your issue. |
That is nice - but is there any way to get the incremented version back from the action, so I do not have to find it in the updated .csproj files? |
Maybe I can store the incremented version in a variable of the action. I will have a try. |
I know actions can have outputs, so thats one way of refering it from the outside. Thanks |
Be good if it could also tag the version :) |
Hi,
Would it be possible for you to make two changes:
I usally commit version updates with a message similar to:
"Update version to 1.2.3"
But the message in this seems to be hardcoded and is not really ideal in my opinion.
I like that you update versions in a file pattern of files and not just a single file, which many of the other "bump" version action does - but because I cannot customize the commit message - or turn it off - I cannot use this.
Onbiously it would require that you add a couple of variables - one for controlling whether or not to commit - and another one where a "template can be set for a commit message" - but the easiest would be to make it possible to turn off committing - then people can just add their own - provided you give the version you updated to in outputs for your action.
Thank you
The text was updated successfully, but these errors were encountered: