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
Is your feature request related to a problem? Please describe.
The token * is the number of commits since .simpleversion.json was changed.
If I am using * each commit increments the version, yet I may only want that on a release branch (where the actual final version is determined). On a feature branch I want the version to to be whatever it is on the branch I branched from, yet count the unique commits on my current branch
Describe the solution you'd like
On master I make five commits. The configuration uses "version": "1.0.*". I will therefore get a version of 1.0.5
I create a branch feature/awesome and complete twenty commits. Using branch overrides, I want to be able to specify that the version created should be 1.0.5-r20
Progress
Calculating base/branch height where version was last modified on release branch
As above, with base version calculated via alternate release branch (e.g release/1.0 instead of master)
Calculating base height where version is changed on the current non-release branch
Calculating base height where version is changed on merged release branch
Calculating base height where multiple release branches are merged out of order. E.g. 1.1.x is merged into feature, then 1.0.x is merged after.
Determine checkout requirements for build servers - Are all refs enough?
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The token
*
is the number of commits since .simpleversion.json was changed.If I am using
*
each commit increments the version, yet I may only want that on a release branch (where the actual final version is determined). On a feature branch I want the version to to be whatever it is on the branch I branched from, yet count the unique commits on my current branchDescribe the solution you'd like
"version": "1.0.*"
. I will therefore get a version of1.0.5
feature/awesome
and complete twenty commits. Using branch overrides, I want to be able to specify that the version created should be1.0.5-r20
Progress
The text was updated successfully, but these errors were encountered: