4 ms·

> Can't use real git hooks. understandable in the shared environment, but an annoyance and it's worth mentioning. It's also worth mentioning that the selection

> Can't use real git hooks. understandable in the shared environment, but an annoyance and it's worth mentioning. It's also worth mentioning that the selection of hooks available pretty much trumps any standard git hooks that I've ever dealt with. And if you really need some custom functionality to fire, you can set up a custom webhook URL that points to your own server somewhere.

oinksoft 14y ago
This then requires exposing a crucial part of your development workflow at a public URL (even if the resource is authenticated). For various reasons, this is quite simply a non-starter for many shops who might otherwise be prepared to bite the bullet and put their source code on Github's servers.
- llimllib 14y ago
  > this is quite simply a non-starter for many shops And, for those people, github offers an appliance that sits on your network.
  - oinksoft 14y ago
    I didn't know github offered an appliance, that sounds like a good fit for those folks as long as it's priced reasonably.
    - Karunamon 14y ago
      It's actually absurdly expensive :( It's a very cool app (Github, only on your own server, basically), but it's priced out of the range of anybody but large enterprises.
  - encoderer 14y ago
    Which is about 10x more expensive than hosted GitHub. No joke.
mh- 14y ago
You're forgetting that there are other types of hooks besides post-receive. "The first script to run when handling a push from a client is pre-receive. It takes a list of references that are being pushed from stdin; if it exits non-zero, none of them are accepted. You can use this hook to do things like make sure none of the updated references are non-fast-forwards; or to check that the user doing the pushing has create, delete, or push access or access to push updates to all the files they’re modifying with the push." http://git-scm.com/book/en/Customizing-Git-Git-Hooks http://git-scm.com/book/en/Customizing-Git-Git-Hooks

oinksoft 14y ago

This then requires exposing a crucial part of your development workflow at a public URL (even if the resource is authenticated). For various reasons, this is quite simply a non-starter for many shops who might otherwise be prepared to bite the bullet and put their source code on Github's servers.

llimllib 14y ago
> this is quite simply a non-starter for many shops And, for those people, github offers an appliance that sits on your network.
- oinksoft 14y ago
  I didn't know github offered an appliance, that sounds like a good fit for those folks as long as it's priced reasonably.
  - Karunamon 14y ago
    It's actually absurdly expensive :( It's a very cool app (Github, only on your own server, basically), but it's priced out of the range of anybody but large enterprises.
- encoderer 14y ago
  Which is about 10x more expensive than hosted GitHub. No joke.

mh- 14y ago

You're forgetting that there are other types of hooks besides post-receive. "The first script to run when handling a push from a client is pre-receive. It takes a list of references that are being pushed from stdin; if it exits non-zero, none of them are accepted. You can use this hook to do things like make sure none of the updated references are non-fast-forwards; or to check that the user doing the pushing has create, delete, or push access or access to push updates to all the files they’re modifying with the push." http://git-scm.com/book/en/Customizing-Git-Git-Hooks http://git-scm.com/book/en/Customizing-Git-Git-Hooks