Incorrect version calculation

[lerthe61]

We have faced some strange behavior, when fork in repository is interpreted as merge:

We also found workaround by changing track-merge-target to false for develop branch.
Original configuration is
GitVersionConfig.zip

We use version 3.4.1 (portable). But issue is still presented in latest codebase.

[lerthe61]

Prepare test repository for illustrating problem. For branch develop GitVersion calculate SemVer "1.0.1-feature.2"
TestRepo.zip

[lerthe61]

Attach unit test for issue. It seems that problem in TrackMergeTargetBaseVersionStrategy.IsDirectMergeFromCommit method.

[pascalberger]

@lerthe61 Can you please test with latest 4.0.0-beta release as it changes some behavior how versioning on develop is handled.

[lerthe61]

@pascalberger Thanks! Everything look ok now. I will create pull request with my test to prevent regression in future