Nicolas Bouchard

I tried to use `{EscapedBranchName}` as the pre-release tag in my GitVersion.yml ```yaml mode: ContinuousDeployment assembly-versioning-scheme: MajorMinorPatch assembly-file-versioning-scheme: MajorMinorPatchTag assembly-informational-format: '{InformationalVersion}' next-version: 1.0.0 #Version à incrémenter manuellement commit-message-incrementing: Disabled branches:...

It seems to fix the problem, but we use this configuration property to control our version manually. It is not a viable option for us to remove it. ``` {...

We use `git tag` only on the main branch, but we want to generate versions during the development process on other branches. We increment the version only when on main,...

No, but if I remove `next-version:` from the Gitversion.yml, which version will be used? I have a version key in my .csproj but it seem to be ignored when gitversion...

I understand, thank your for the explanation. Seems we will have to use `git tag` as a required step in our team developement workflow. I know it is a good...