You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use GitVersion to generate the version number for this project. Actually the plan is to use the GitHub Action. GitVersion will be setup to support the Cactus Branching model (see below for details) which requires a setup like:
The idea is that only release-X.Y branches are tagged something like vX.Y.Z. Then this tag is merged back to main GitVersion will calculate the next version number as vX.Y+1.0.0.
When a feature branch is merged to release-X.Y for a bug fix only the patch number will be incremented and the major, minor, and patch numbers left as is.
GitVersion generates several different version number formats such as:
AssemblySemVer: 0.8.0.0
NuGetVersionV2: 0.8.0-alpha0001
MajorMinorPatch: 0.8.0
GitVersion can set the version in C# Assembly Version files now that they have fixed this issue.
An example of the Cactus or Trident Branching model:
The text was updated successfully, but these errors were encountered:
Use GitVersion to generate the version number for this project. Actually the plan is to use the GitHub Action. GitVersion will be setup to support the Cactus Branching model (see below for details) which requires a setup like:
The idea is that only
release-X.Y
branches are tagged something likevX.Y.Z
. Then this tag is merged back tomain
GitVersion will calculate the next version number asvX.Y+1.0.0
.When a feature branch is merged to
release-X.Y
for a bug fix only the patch number will be incremented and the major, minor, and patch numbers left as is.GitVersion generates several different version number formats such as:
GitVersion can set the version in C# Assembly Version files now that they have fixed this issue.
An example of the Cactus or Trident Branching model:
The text was updated successfully, but these errors were encountered: