You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.dirnamebut should this be the behavior forgit.Repoto need the top level of a repo or a bug?