Use GitVersion (Mainline development mode) for semantic versioning in Azure DevOps using Git Hooks

This is tested for Basic Merge (no Fast forward) Pull Request Merge Type.
There are four different ways to consume GitVersion itself. You can find each of these options - gitversion.net/docs/usage/
Install GitVersion on Azure DevOps Self hosted agent - gitversion.net/docs/usage/cli...
OR
Install Azure DevOps extension - marketplace.visualstudio.com/...

[@tommiwiren2405]

Excellent video! Thank you!

[@raghur5678]

Hi thanks for the video.. i have one problm like when i am running on my feature branch the Tag version is 1.0.1, whn merging with the Develop Branch its getting changed to 271.1.0,but i want to be with 1.0.1 version for the Client SDK and the Data N Service Dll... but why its getting changed? any idea

[@raaviblog105]

Is develop branch your mainline branch?

[@raghur5678]

@@raaviblog105 MAster is the production code where we stored.,we have different branching strategies where we have feature,develop and Master.

[@timmkrause6684]

Instead of using a Git hook which every developer needs to configure wouldn't it be better to control this via the GitVersion.yml as well? branches: feature: increment: Minor

[@timmkrause6684]

Does work for builds from the feature branch, but not for builds for PRs... PR build versions still only increment patch version in this case, so the Git hook is really needed to bump minor as well for PR builds.

[@timmkrause6684]

With the config part from above I get this: feature/another-test -> 1.6.0-another-test.1 PR build: 1.4.14-PullRequest2651.2

[@elvargas1327]

I don't understand why my minor 'feature' never changes

[@raaviblog105]

Is it not changing even after adding [+semver:minor].can u explain your setup then may be I can help

[@elvargas1327]

@@raaviblog105 It worked for me, could you tell me if I'm right? When the change comes from an origin configured in source-branches, does the increment respect the value configured in increment, otherwise it only increases in Patch? For example: main: regex: main tag: '' source-branches: ['main','master'] prevent-increment-of-merged-branch-version: false track-merge-target: false tracks-release-branches: false is-release-branch: false release: regex: release(s)?[/-] tag: beta increment: Minor source-branches: ['main','master'] prevent-increment-of-merged-branch-version: true track-merge-target: false tracks-release-branches: false is-release-branch: true main only increment in Patch, but if realease receives a change from main it increases by minor?

[@raaviblog105]

I haven't tried with Release branch. With Mainline development, the increment of minor or patch happens at the time of merge into Main branch. this link can give some more info -gitversion.net/docs/reference/modes/mainline