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

GitPython not returning error #271

tardis4500 opened this Issue Mar 20, 2015 · 2 comments


None yet
2 participants

tardis4500 commented Mar 20, 2015

When I run the command from the command line
git push -u --all origin
it fails with
remote: import failed: User not permitted to commit
and exit code of 1.

But doing the same thing programmatically in GitPython does not show any error at all even though I can see the push was unsuccessful because the changes were not pushed.

@Byron Byron added the acknowledged label Mar 20, 2015

@Byron Byron added this to the v0.3.7 - Fixes milestone Mar 20, 2015


This comment has been minimized.


Byron commented Mar 20, 2015

I believe to have found the source of this issue: For some reason, it will only treat exit code 128 as error, as can be seen here.

This should probably just re-raise - at least I can't see why there is this kind of special treatment.

@Byron Byron self-assigned this Apr 8, 2015

Byron added a commit that referenced this issue Apr 8, 2015

fix(docs): be clear about exit code handling
When pushing/pulling, we ignore errors unless it's exit code 128.
The reason for this is now made explicit to make clear that issues
are handled by PushInfo flags accordingly.

Related #271

@Byron Byron closed this in e9f8f15 Apr 8, 2015


This comment has been minimized.


Byron commented Apr 8, 2015

You can watch the development stream on youtube.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment