Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question] Is this Version flow possible? #1295

Closed
JonCubed opened this issue Sep 22, 2017 · 3 comments
Closed

[Question] Is this Version flow possible? #1295

JonCubed opened this issue Sep 22, 2017 · 3 comments

Comments

@JonCubed
Copy link
Contributor

I've been playing around with GitVersion trying to get the following version calculation flow to work

master
  * (HEAD, calulated version: 1.1.0)
  |
  * (tag: release/v1.0.0, calculated version: 1.0.0)
  |
  * (calulated version: 0.4.1)
  |\
  | \
  |  * (branch: feature/bar, calculated version: 0.4.1-bar)
  |  |
  |  * (branch: feature/bar, +semver: patch, calculated version: 0.4.1-bar)
  | /
  |/
  * (calulated version: 0.4.0)
  |\
  | \
  |  * (branch: feature/foo, calculated version: 0.4.0-foo)
  |  |
  |  * (branch: feature/foo, calculated version: 0.4.0-foo)
  | /
  |/
  * (calculated version: 0.3.0)
  |
  * (calculated version: 0.2.0)
  |
  * (initial commit, calculated version: 0.1.0)

but haven't had much luck. Is it possible with v3 or v4?

It seems like I want to use Mainline but that seems to only increment Patch and I want it to increment Minor

@asbjornu
Copy link
Member

@JonCubed: Can't you just set the increment configuration property to Minor?

@JonCubed
Copy link
Contributor Author

@asbjornu I've tried that but it only increments Patch regardless what I have as increment

@JonCubed
Copy link
Contributor Author

I've dug into the code tonight and this seems to be a bug with Mainline version calculation defaulting to Patch if no message bump is found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants