-
Notifications
You must be signed in to change notification settings - Fork 35
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
hook create fails? #8
Comments
Hi Robert, thanks for using the library and reporting the issue. Sorry for the frustrating experience. I'm in the process of rewriting it and release updates frequently. I haven't looked into hook command yet but will jump on it this evening if you can wait. |
No worries, just wasn't sure whether it works and I was missing something, or whether there was a bug! 😃 |
All hook commands should be fixed now, just released
Help should also be clearer, the array params are just strings delimited by space. Similarly, the hash config consists of key:value pairs separated by space. I still expect to find some bugs as this library is going through quick development, however I'm testing it thoroughly to crash all bugs with my test detergent 😄 If you have any observations/suggestions on using this library please post them on this issue tracker and I will be more than happy to look into them. I particularly appreciate usability/interface comments. |
Didn't seem to work (just created as |
I'm running the following: |
Because I wanted to register a hook for both status & push events. On Monday, 15 April 2013, Piotr Murach wrote:
|
You can supply array elements separated by space so in your case |
Really? that's some crazy arg-parsing behaviour! Thanks, will give it a go On Mon, Apr 15, 2013 at 7:16 AM, Piotr Murach notifications@github.comwrote:
|
Any luck Robert? |
Hi Robert, I am gonna close this issue as |
I'm all out of ideas...
It's not clear from the help/docs/etc whether
--name=me
or--params=name:me
or-p name:me
is the right way to specify parameters, let alone how to specify an array/hash as a parameter.The text was updated successfully, but these errors were encountered: