Replies: 3 comments 2 replies
-
I'm not opposed to this idea. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I'll have a go ;-) |
Beta Was this translation helpful? Give feedback.
0 replies
-
Do you need to open the feature so I can issue the PR - all I seem to be able to do is open an issue |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I (almost) understand the reasons for dropping
NugetVersion2
but it leaves us with the problem of getting an acceptable version number into this and other package managers. The new formatting capabilities developed by @9swampy are great but we are left with getting it into the output, my current approach changing the format ofassembly-informational-format
works, but distorts that value.What I'm suggesting is introducing a new variable to be computed which defaults to
{SemVer}
but can be changed in the configuration/parameters. This avoids changing existing variables and allows case-specific scenarios to be applied without introducing lots of different variables as I think the likelihood of needing more than one custom format not already covered is low.The reason I'm suggesting a new variable is to compute this inside GitVersion using the information is has, rather than trying to compose it outside in a build server with the possibilities of additional formatting challenges.
Don't care what the name is
UserVersion
is a first-thoughtBeta Was this translation helpful? Give feedback.
All reactions