-
Notifications
You must be signed in to change notification settings - Fork 41
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
Does not work with local remotes #56
Comments
That's really interesting, thanks for reporting! I suspect that the new GitPython release v2.0 somehow breaks PyGitUp as it seems to have worked fine with v1.0. I'll investiage this. BTW also breaks the test suite as it too uses local remotes 😄 |
msiemens
added a commit
that referenced
this issue
Nov 3, 2016
Up to now, we specified GitPython >= 1.0.2 which included v2.0 which changed its implementation details so it broke our error handling. Now we don't depend on GitPython's `GitCommandError` any more as there was no real need to subclass it anyway. Not fully tested on my machine, will see if this actually fixes it. See #56
Seems to be fixed in 2aa1190, I'll release a new version of PyGitUp soon :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I know that sounds strange. But if you have a local directory as one of your remotes, the script fails:
To reproduce:
The text was updated successfully, but these errors were encountered: