{"action":"opened","issue":{"url":"https://api.github.com/repos/GitTools/GitVersion/issues/1728","repository_url":"https://api.github.com/repos/GitTools/GitVersion","labels_url":"https://api.github.com/repos/GitTools/GitVersion/issues/1728/labels{/name}","comments_url":"https://api.github.com/repos/GitTools/GitVersion/issues/1728/comments","events_url":"https://api.github.com/repos/GitTools/GitVersion/issues/1728/events","html_url":"https://github.com/GitTools/GitVersion/issues/1728","id":462405259,"node_id":"MDU6SXNzdWU0NjI0MDUyNTk=","number":1728,"title":"Mainline: Starting new release branch from develop results in unexpected version increment","user":{"login":"NightOwl888","id":1538288,"node_id":"MDQ6VXNlcjE1MzgyODg=","avatar_url":"https://avatars2.githubusercontent.com/u/1538288?v=4","gravatar_id":"","url":"https://api.github.com/users/NightOwl888","html_url":"https://github.com/NightOwl888","followers_url":"https://api.github.com/users/NightOwl888/followers","following_url":"https://api.github.com/users/NightOwl888/following{/other_user}","gists_url":"https://api.github.com/users/NightOwl888/gists{/gist_id}","starred_url":"https://api.github.com/users/NightOwl888/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/NightOwl888/subscriptions","organizations_url":"https://api.github.com/users/NightOwl888/orgs","repos_url":"https://api.github.com/users/NightOwl888/repos","events_url":"https://api.github.com/users/NightOwl888/events{/privacy}","received_events_url":"https://api.github.com/users/NightOwl888/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-06-30T13:28:12Z","updated_at":"2019-06-30T13:28:12Z","closed_at":null,"author_association":"NONE","body":"This is my first crack at GitFlow, so I am trying to follow [the docs](https://nvie.com/posts/a-successful-git-branching-model/) as much as I can. So, I am not sure if this is a bug with GitVersion or something I am doing wrong.\r\n\r\nHere is the scenario:\r\n\r\n1. master at version 1.2.152 (tagged)\r\n2. `git checkout -b develop master` -> results in build of version `1.3.0-alpha.1` (as expected)\r\n3. New commit added to develop -> results in build of version `1.3.0-alpha.2` (as expected)\r\n4. `git checkout -b release-1.3 develop` -> results in build of version `1.3.1-beta.2` **(expected `1.3.0-beta.1`)**\r\n5. New commit added to release-1.3 -> results in build of version `1.3.1-beta.3` (as expected)\r\n\r\nDo note, my plan is to **only tag stable prereleases and releases (after the release)**, so no other tags than on the master branch have been used during this simple scenario. There are also no commits tagged with `+semver:`.\r\n\r\nI have tried the following release branch formats, but always get the version number `1.3.0-beta.1`\r\n\r\n```\r\nrelease/v1.3\r\nrelease/1.3\r\nrelease/1.3.0\r\nrelease-1.3.0\r\nrelease-1.3\r\n```\r\n\r\n### GitVersion.yml\r\n```\r\nmode: Mainline\r\nassembly-versioning-scheme: Major # Use strong-named assembly version format always (even when not strong naming)\r\nassembly-informational-format: '{NuGetVersion}.Branch.{BranchName}.Sha.{ShortSha}'\r\nbranches: {}\r\nignore:\r\n  sha: []\r\n```\r\n\r\nI have read #695, but that only seems to have applied when `alpha` was named `unstable`. Now that it is `alpha`, I would expect the version incrementing to be correct.\r\n\r\nWhy is the release branch not calculating the expected version number in this case?"}}
{"actor":{"display_login":"NightOwl888"}}