-
Notifications
You must be signed in to change notification settings - Fork 654
Sequence contains more than one matching element #453
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
Comments
Are you able to check if master has the same issue? There are a few fixes to still go in around this particular class, but there have been a few already |
master builds without the same issue. |
Great. I am working on getting beta3 out over the weekend. Will let you know once out |
perfect thanks. Interestingly, I've just forced the build on that same PR (after making some other unrelated commits and merges) and it's built ok with a build number of 2.0.2-PullRequest.5+3. Note the patch has incremented. |
I think that is the same as this: #415 |
Pretty sure this is fixed |
In master that is, next release should not have the PR version issue |
I am getting this error from TeamCity running "GitVersion 3.0.0-beta0002":
I created branch, committed and pushed, created a pull request against a branch and then committed an additional change to that branch.
GitVersion parses the original commit (2.0.1-abc.1+1), the first PR (2.0.1-PullRequest.5+2) and the second commit (2.0.1-abc.1+2) but throws the above exception when parsing the PR. There are 3 tags against the repo.
The text was updated successfully, but these errors were encountered: