Skip to content
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.

Sign up for GitHub

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

Jump to bottom

GitCommandError doesn't capture stdout #90

Closed
msiemens opened this issue Jan 17, 2013 · 1 comment
Closed

GitCommandError doesn't capture stdout #90

msiemens opened this issue Jan 17, 2013 · 1 comment

Comments

@msiemens
Copy link
Contributor

When calling repo.git.rebase('origin/master') and the command fails, a GitCommandError is thrown. But the command's output is not captured there because it seems like git rebase always prints to stdout.
My suggestion is to add a stdout variable to GitCommandError to capture this output, too.
@msiemens msiemens mentioned this issue Jan 17, 2013
Closed
@msiemens
Copy link
Contributor Author

Sorry for the duplicate bug entries, #91 was the first Pull Request I ever made in GitHub and did't know, it will create a bug entry, too, so please close this bug ticked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@msiemens