Hardy Hobeck
Hardy Hobeck
I think this test illustrates the problem very well: ```csharp [TestCase("0.3.0-alpha.1+4", false)] [TestCase("0.3.0-alpha.1+1", true)] public void VersionSource(string semanticVersion, bool removeReleaseBranchAfterMerging) { // Arrange var configuration = GitFlowConfigurationBuilder.New .WithBranch("develop", _ =>...
If I execute the following integration test then I cannot see any problems. This issue might be solved. ```csharp [Test] public void __Just_A_Test__() { var configuration = GitFlowConfigurationBuilder.New.WithNextVersion("1.2.0").Build(); using var...
> When invalid file name passed to the -config switch (missing file, etc...) no error message is shown and GitVersion silently assumes default configuration. I think this statement is confusing...
> Well, there are probably people out there who rely on this behavior ([Hyrum's Law](https://www.hyrumslaw.com/)), but I'm not sure if keeping it worth the trouble. In my opinion it makes...
Hi there. What I'm confused about: If you are defining a different separator then the result is not a semantic version number anymore. I want to point out that the...
If you see the following figure then we have alread a fallback mechanism:  Unfortunately the branch related property `PreReleaseWeight` defaults to zero if it has not been specified. Thus...
@tobiasdiez Could you please provide us an integration test to illustrate and ensure your scenario? Please take the version from main branch. ```csharp [Test] public void IntegrationTest() { var configuration...
Okay great idea. Please feel free and implement this feature if you need this and provide a PR. :)
Has been resolved with PR https://github.com/GitTools/GitVersion/issues/2336 without the need of specifing IsRelease to true for Hotfix branches.
It is not possible to verify your issue when no information about the status of your repository and the used configuration is documented. Probably the configured branch label does not...