[Feature] Do not fail AppVeyor builds on force-push

[nils-a]

I'm always frustrated when my build fails. 😁

When force-pushing (which is a nasty habit of mine) the same version as for the previous build is generated. This is fine.
However, AppVeyor builds then fail in GenerateSetVersionMessage with a (500) Internal Server Error.

Detailed Description

My guess is that this is due to the fact that the build can not be renamed to a name that has already been used.
One example of a fail is here: https://ci.appveyor.com/project/cakebuild/cake-rider/builds/41107162#L319

Context

While I really do like the feature that builds are "named" with version numbers in appVeyor, I'd rather not have the whole build fail when that does not succeed.

Possible Implementation

One possibility (fast and simple, good for me, not necessarily good for everyone) would be to try-catch the EnsureSuccessStatusCode and return a different message.

[arturcic]

I agree with the solution, are you in a position to send a PR with the change?

[nils-a]

Sure.

[github-actions]

🎉 This issue has been resolved in version 5.8.0 🎉
The release is available on:

• GitHub Release
• Chocolatey Package
• .Net Global Tool

Your GitReleaseManager bot 📦🚀