Stack overflow due to infinite loop falling back to branch config

[sumo300]

In a repository that only has a master and a release branch, during a pull request build (TFS 2018 Update 2), GitVersion goes into an infinite loop and eventually errors out with a stackoverflow error.

This happens with both 3.6.5 and the latest 4.0.0 version (4.0.1 version of the VSTS task and using the latest version of GitVersion from Chocolatey).

I have attached the GitVersion.yml file and the logs from our latest failing build. This yml config fixes the issue by forcing pull requests to use Patch rather than Inherit for the increment setting. When it defaults to Inherit, it cannot figure out the fallback version.

GitVersion-log.zip
GitVersion.yml.zip

[sumo300]

This is now failing on a build with the 4.0 version of GitVersion on a tagged build. This should not happen if I'm interpreting the docs correctly.

[sumo300]

Another update. On the repo we had issues, we did a massive branch clean-up, and this seems to have helped for now.

[sumo300]

This problem will just not go away. Any chance at all there is a potential fix for this issue?

[PavelDanov]

I've also encountered this issue recently. Will GitVersion support Microsoft's Release Flow as a first-class citizen eventually?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. Thank you for your contributions.

[thepirat000]

So you will never fix this

[Huffers]

This happened to me on a merge commit.
I was able to workaround the issue by switching the parents of the merge commit, using this stack overflow answer.

[asbjornu]

@thepirat000, there is no "you", it's "we". No one is getting paid to work on GitVersion, so unless someone submits a pull request to fix this issue, it's not going to get fixed. So far we haven't gotten a single reproduction, not a public repository where the problem exists, not a TestFixture, nothing. Until we do, this bug will persist.

[HHobeck]

Hi there. I'm going to close this issue because no one is providing steps to reproduce. In advance the whole mechanism to determine the branch configuration has been changed. Thus this should not happened in version 6.x anymore. Please reopen this issue or create a new bug if the stack overflow issue still persists.

Cheers.