Struggling with Nerdbank #GitVersioning to do what I want it to do. Seems quite a simple task but for some reason I can't manage it.
I want it to increase the fourth version number upon a commit into master. I don't care what happens on non-master branch, it might be like 1.0.0-dev.123 or whatever, but the Master branch must be clean and must have increasing builds, like: 1.0.0.1, 1.0.0.2, 1.0.0.3 etc.
If anyone has any ideas, I'm all ears. #DotNet #Version
I want it to increase the fourth version number upon a commit into master. I don't care what happens on non-master branch, it might be like 1.0.0-dev.123 or whatever, but the Master branch must be clean and must have increasing builds, like: 1.0.0.1, 1.0.0.2, 1.0.0.3 etc.
If anyone has any ideas, I'm all ears. #DotNet #Version
Jimmy
in reply to André Polykanine • • •since NBGV uses the git height, every merge to master must be squashed to get sequential x.x.x.1, x.x.x.2. Non-squashed merges will jump the final value by the merged height.
Then set your version value to "1.0.0" in version.json. This will set it to use a 4 segment build number for file versions instead of the default 3 segments. Nuget package version will still only have 3 segments.
If you want to get a x.x.x.0 build on major versions (instead of x.x.x.1), you need to offset the initial commit height. You can set buildNumberOffset to -1 for this.
André Polykanine
in reply to Jimmy • • •