-
Notifications
You must be signed in to change notification settings - Fork 53
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
Versioning - Add ability to override generating versioning information #217
Comments
Comment from @AdmiringWorm in duplicate issue... Or maybe in a Setup instead, which can be conditionally disabled by the user if they want.
|
gep13
added a commit
to gep13/Cake.Recipe
that referenced
this issue
Jul 9, 2020
When you want to use something other than GitVersion to perform the versioning of the repository, you can override the new Setup method, and as long as you provide a BuildVersion instance, the remainder of the code should work as expected.
gep13
added a commit
to gep13/Cake.Recipe
that referenced
this issue
Jul 9, 2020
When you want to use something other than GitVersion to perform the versioning of the repository, you can override the new Setup method, and as long as you provide a BuildVersion instance, the remainder of the code should work as expected.
gep13
added a commit
to gep13/Cake.Recipe
that referenced
this issue
Jul 9, 2020
When you want to use something other than GitVersion to perform the versioning of the repository, you can override the new Setup method, and as long as you provide a BuildVersion instance, the remainder of the code should work as expected.
gep13
added a commit
to gep13/Cake.Recipe
that referenced
this issue
Jul 9, 2020
When you want to use something other than GitVersion to perform the versioning of the repository, you can override the new Setup method, and as long as you provide a BuildVersion instance, the remainder of the code should work as expected.
AdmiringWorm
added a commit
that referenced
this issue
Jul 9, 2020
(GH-217) Add ability to override versioning
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thinking of being able to do something like this:
This would enable you to build custom versioning schemes, use other tools as dropin replacements for GitVersion, or customise the GitVersion options completely.
The text was updated successfully, but these errors were encountered: