Create serverside git hooks

Depending on the scope and difficulty of the changes, there's probably a point at which it would be worth waiting until we can generate a gitlib (analogue to svnlib) that'll make doing those operations easier. I dunno how many or how complex changes you have in mind, though, so I'm just throwing that out there as a general note.

need these, BIIIIG time, for phase 2 of the migration.

well actually, we may end up implementing the hooks we want in the drupalorg module, or something less generic than vcsapi. but until that decision is made, i'm tagging this issue accordingly.

related: #973944: Integrate GSoC 2009 Daniel Hackney work, IIRC that was one of the main goals for Daniel

another related: #730738: chdir() call leads to fatal error because files can't be included anymore.

We're going to be writing some serverside git hooks in sprint 8 - though they'll probably end up being entirely d.o specific. Hence this issue in infra: #1012988: Create serverside git hooks that interact with our unique server environment. We need to update these before we can make a stable release, though.

If you can't help Sam with this, would you please reassign it to him?

We don't need this for launch, since we use our own custom set of hooks that are really quite distinct from anything that would be useful generically. Untagging, and not tagging for phase 3.

We need something in vc_git for it to be set for a stable release, I think, but that's a separate priority.

removing sprint 9 tag

@sdboyer: Probably related with your current work? (IIRC it would be generalizing it?)

Yeah, this dovetails with generalizing the history sync mechanism and some of the new methods added to that interface. We may need to decide on what our "out of the box" target use case is for these to be really useful...maybe not. We might be able to get away with a single generic set.

Not sure about the status of this, but before git hook scripts for d.o ended up managed with puppet directly they were on the drupalorg project, so pasting here a: link there.

The basic workflow is covered!

See

• Add a DEAD-simple post-receive, really just for testing purposes.
• Improve and document the serverside git hook script provided as example.