Hanzo
OpenapiGit

Accept a push, and turn it into a build — POST /v1/git/{org}/{project}/{repo}/git-receive-pack

The pack-transfer phase of a push, and the point at which a push becomes an EVENT.

POST /v1/git/{org}/{project}/{repo}/git-receive-pack

Addresshttps://api.hanzo.ai/v1/git/{org}/{project}/{repo}/git-receive-pack
MethodPOST
Operationpost_git_by_org_by_project_by_repo_git-receive-pack
AuthAuthorization: Bearer $HANZO_API_KEY

The pack-transfer phase of a push, and the point at which a push becomes an EVENT. NEVER ANONYMOUS: a push always requires an authenticated org, and the org in the path must equal it.

Once the pack is on disk the repository's storage usage is metered and a build is fired for every branch whose tip actually moved, computed from the before/after branch diff rather than from what the client claimed. That runs on a cancel-immune context, so a client that hangs up the moment its push lands still gets its build, and it runs even when git itself exited non-zero — the refs on disk are the ground truth. Repacking housekeeping is detached and never blocks the response.

A Content-Type other than application/x-git-receive-pack-request is 400. Addressed under the API prefix, with the PROJECT as a middle path segment: project scope otherwise rides a header a git client cannot send, so this path is the only usable remote for a project-scoped repository. This is git's own wire protocol, not an API call to make by hand: point a git client at the clone URL and it makes this request itself.

Request

4 fields, body application/octet-stream.

FieldInTypeRequiredDescription
orgpathstringyes
projectpathstringyes
repopathstringyes
(body)bodystring (binary)yes

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo git org project git-receive-pack <org> <project> <repo>

Git API · All Hanzo APIs · Interactive reference

How is this guide?

On this page