Updated IncrementStrategyFinder to support version bumping from tags

[MikeEvansLarah]

Updated IncrementStrategyFinder to support version bumping from tagged commits.

Updated tests and docs.
#971

[pascalberger]

Remove double linebreak

[pascalberger]

Thanks for your contribution! LGTM

@asbjornu @gep13 @JakeGinnivan OK for you too merge this?

[JakeGinnivan]

Would you be able to walk me through a typical workflow on how you would use this feature @MikeLarah?

[JakeGinnivan]

@MikeLarah am keen to hear more about the requirements for this change?

[MikeEvansLarah]

@JakeGinnivan Sorry for the delayed response. Our intention was to use this in combination with a process in the CI build that determined whether the public API has been changed.
e.g. 1) developer commits and pushes up changes to a feature branch, 2) CI build does comparison between feature branch binaries and latest master binaries to determine if API has changed, 3) we tag the commit with relevant major/minor increment tag if necessary, 4) future builds are automatically version incremented using GitVersion (and will be correctly incremented when the feature is merged to develop branch)

[JakeGinnivan]

Hey Mike,

I see a few issues with this approach

1. More config :(
2. git tag will have a heap of +semver-minor tags, which is noisy

Alternatives:

When you merge pull requests, you can alter the merge message in every tool I know. At that point simply append +semver: minor to the merge PR commit message.

Then you can use the new Mainline development mode in v4 to aggregate the versions from each merged PR. I think your process is working around the fact mainline was missing and I think it should be able to solve your problem. Let me know how you go, going to close this out for now (but we can keep the convo open)