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.

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

Access to the stdin lines as described by Git #28

Open
dualcyclone opened this issue Jun 15, 2015 · 1 comment
Open

Access to the stdin lines as described by Git #28

dualcyclone opened this issue Jun 15, 2015 · 1 comment

Comments

@dualcyclone
Copy link
Contributor

Would be really useful if we could get hold of the actual input used when running pre-push as described here:

http://git-scm.com/docs/githooks#_pre_push

...and used in action in the sample here:

https://github.com/git/git/blob/master/templates/hooks--pre-push.sample

Seems git itself takes control of the stdin; I've had a look at least, and cannot seem to access this information cleanly, if at all.

Would certainly be useful to ascertain the actual branch being pushed, as it would be possible for a user to push a branch that is different to their current active branch.

@bahmutov
Copy link
Owner

bahmutov commented Aug 4, 2015

hmm, mind making a test case for this and submitting as a pull request?

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

No branches or pull requests

2 participants