-
-
Notifications
You must be signed in to change notification settings - Fork 933
tests fail if reflog is empty #286
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
This is a known issue, and is currently overcome by preparing the repository after checkout, on travis at least. Feel free to suggest a solution, however, to me it seems the main culprit is that GitPython uses its own repository in read-only mode at all. This is bad and shouldn't be done, but also speeds up tests considerably. One could consider rewriting tests to setup their own sandboxes from scratch, but so far I didn't get around that. Thus, to me this issue is "won't fix", but I am open to suggestions if they don't involve a massive amount of work coming my way :). |
Sorry for forgetting about this. I don't really have an idea of how to fix this, so we just use something similar to what travis does in our package for now. |
No need to apologize, I am happy you got it to work on your end. |
When the reflog for the current branch has only 1 entry (I don't think "empty" is technically possible), tests fail with
If I for example create an empty commit with
they pass.
You can reproduce this easily by cloning the GitPython repo to a new directory.
The text was updated successfully, but these errors were encountered: