-
Notifications
You must be signed in to change notification settings - Fork 650
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
nullref in GitRepoMetadataProvider.FindMergeBase #1230
Comments
so seems adding
and letting the loop fall out, results in the correct version number. do u want a PR for that? |
@SimonCropp: Yes, that would be nice. A warning that no merge base was found should also probably be written, no? |
@JakeGinnivan polite request for a release ;) |
@asbjornu @gep13 @pascalberger can we get a release of this? Also as an aside any eta on the next stable release? |
Has this been released? I've been seeing this too. Also, weirdly, I get this locally but not on AppVeyor 🤔 |
Yes, as a99f256 shows, this should be in |
@asbjornu The latest release on nuget.org is 4.0.0-beta0012. Beta 13 was never released. |
@asbjornu Is the mean time, would it be possible to manually release a new package? In fact, I'd like to see a beta 14 released that incorporates the latest changes. Beta 13 was tagged before a lot of important changes. |
@bording: I would love to, I just don't understand how. If I did, I would have made many releases already. |
this is with current the current master as at 30f413a
Still trying to grok why. but here is the debug state to start with. seems
Repository.ObjectDatabase.FindMergeBase
returned nulland here is the trace
The text was updated successfully, but these errors were encountered: