-
Notifications
You must be signed in to change notification settings - Fork 652
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
Add additional output type for saving asserted version numbers to a file #983
Comments
@gep13 Hi. I would like to work on this issue. Please let me know if I may. I am a beginner and this would be my first contribution to open source. |
@kritisingh1: Awesome! Please go ahead and:
If you have any questions, don't hesitate to ask them here or on Gitter. |
Is this issue still up for grabs? I might try and have a stab at it in my minimal spare time. |
@WhiteWaterCoder: Yes, absolutely! That would be awesome! |
This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. Thank you for your contributions. |
🎉 This issue has been resolved in version 5.3.0 🎉 Your GitReleaseManager bot 📦🚀 |
It would allow some consistency when calling GitVersion with
/output buildserver
where the variables are not output to the stdout, since this is not possible.We are already creating the cache file on each run, so it should be simple enough to take a file path from the user, and save the file there also.
As discussed on Gitter here:
https://gitter.im/GitTools/GitVersion?at=5799fe2c93148c6b21e580a5
The text was updated successfully, but these errors were encountered: