Skip to content

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

Closed
malford opened this issue Feb 9, 2015 · 3 comments
Closed

git.Repo InvalidGitRepositoryError #255

malford opened this issue Feb 9, 2015 · 3 comments

Comments

@malford
Copy link

malford commented Feb 9, 2015

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:

Traceback (most recent call last):
  File "/path/to/repo/sub_dir/perc_version", line 685, in <module>
    main()
  File "/path/to/repo/sub_dir/perc_version", line 567, in main
    perc_lib.fail_if_outdated()
  File "/path/to/repo/sub_dir/lib.py", line 451, in fail_if_outdated
    repo = git.Repo(os.path.dirname(command_path))
  File "/usr/local/lib/python2.7/site-packages/git/repo/base.py", line 162, in __init__
    raise InvalidGitRepositoryError(epath)
git.exc.InvalidGitRepositoryError: /path/to/repo/sub_dir

I can fix by adding another os.path.dirname but should this be the behavior for git.Repo to need the top level of a repo or a bug?

@Byron Byron added this to the v0.3.7 - Fixes milestone Feb 9, 2015
Byron added a commit that referenced this issue Feb 9, 2015

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
Related to #255
@Byron
Copy link
Member

Byron commented Feb 9, 2015

This is related to a bug-fix actually. To get the old behaviour, you can instantiate your Repo object with Repo(path, search_parent_directories=True).

The change was noted in the changelog for v0.3.5.

Please let me know if this fixes your issue.

@malford
Copy link
Author

malford commented Feb 9, 2015

Yes, that fixes it. Thanks @Byron!

@ofloveandhate
Copy link

i got the same error as OP when trying to make a git.Repo from a subdir of a git repo. this thread solved it for me. Namely,

Repo(search_parent_directories=True)

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
Development

No branches or pull requests

3 participants