For proper operation of the hook scripts, we need to create some drush commands that can take arguments of the sort generated by the data that typically passes through serverside git hooks. So, the sort of data being discussed in #878278: Conceive of tests for all possible receive-pack related hooks (pre-receive, update, post-receive, and post-update).

These drush commands will probably just be thin wrappers on repo methods that fetch & parse specified commit ranges. We'll also prolly need these to be sensitive to non-ff pushes...if not now, then very VERY soon.

Comments

Anonymous’s picture

subscribe.

Anonymous’s picture

sdboyer’s picture

Issue tags: -git sprint 8 +git sprint 9

Pushing this back to sprint 9. Yeah, it's critical, but we've got other things to focus on at the moment which are in the way of even really being able to push.

jonathan webb’s picture

Assigned: sdboyer » jonathan webb
jonathan webb’s picture

Status: Active » Needs work
StatusFileSize
new2.76 KB

Here's a sketch for the drush integration side of things... This patch includes two drush commands corresponding to the server-side "pre-receive" and "update" hooks. Just checking if I'm on the right track here.

eliza411’s picture

Leaving this open as it may become enough or may need work depending on the out come of performance testing.

sdboyer’s picture

Issue tags: -git sprint 9 +git sprint 10
eliza411’s picture

sdboyer’s picture

Status: Needs work » Closed (fixed)

we've had these forever; this never got closed.

marvil07’s picture

Project: Version Control API -- Git backend » Version Control API
Component: Code » Drush integration
Status: Closed (fixed) » Closed (duplicate)