-
Notifications
You must be signed in to change notification settings - Fork 652
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] ignore parameter does not ignore everything #3074
Comments
Although I don't see the value of this, I agree that ignoring the entire repository should yield a |
I'm also in need of this and started a branch here https://github.com/rominator1983/GitVersion/tree/fix/IgnoreAllCommits_Issue3074 to make a PR The value of this (at least that's what I hope) is to mitigate erroneous commits. I was wondering about the tests. I ran the tests 3 locally and got 21 (for tag 5.10.3) or 10 (main) red tests. Here is an example of a broken test. NextVersionCalculatorTests.PreReleaseNumberShouldBeScopeToPreReleaseLabelInContinuousDelivery:
Also I tried to run a documentation build as described in So this makes it difficult for me to tell if my changes are fine or if existing tests need to be adapted because of a changed behavior. |
@ibvhefe you think you could try if the PR fixes your issue? |
@rominator1983 thanks a lot for caring and providing a fix. Unfortunately I am on vacation and do not have access to a computer. I can try it out in two weeks. Sorry |
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. |
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. |
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. |
Actually if you specify some date in the future the behaviour of GitVersion should be throwing an exception because it is equivalent to the case you have an empty repository. GitVersion needs at least one commit to determine a semantic version. @asbjornu: Are you agree? |
@HHobeck, I think it's debatable whether GitVersion should always try to produce a version number, even in obvious invalid circumstances (such as the repository having no reachable commits, missing |
🎉 This issue has been resolved in version 6.0.0-beta.7 🎉 Your GitReleaseManager bot 📦🚀 |
Describe the bug
Expected Behavior
A version such as
0.1.0
Actual Behavior
The calculated version seems to be too high:
The text was updated successfully, but these errors were encountered: