- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 933
git.Repo InvalidGitRepositoryError #255
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
Labels
Milestone
Comments
This is related to a bug-fix actually. To get the old behaviour, you can instantiate your The change was noted in the changelog for v0.3.5. Please let me know if this fixes your issue. |
Yes, that fixes it. Thanks @Byron! |
i got the same error as OP when trying to make a
|
ofloveandhate
pushed a commit
to ofloveandhate/b2
that referenced
this issue
Feb 15, 2018
the documentation now depends on gitpython -- though sphinx will merely fail to generate the version numbers if it is not present. thanks to * Jim Easterbrook's reply in https://groups.google.com/forum/#!topic/sphinx-users/9eBpfT-WEmY and * gitpython-developers/GitPython#255
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Previously when using GitPython 0.3.2c1 we had something that would point to a sub directory in a repo:
repo = git.Repo(os.path.dirname('/path/to/repo/sub_dir'))
Now after upgrading to GitPython 0.3.6 I am getting this error:
I can fix by adding another
os.path.dirname
but should this be the behavior forgit.Repo
to need the top level of a repo or a bug?The text was updated successfully, but these errors were encountered: