Repacks a repo into one bitmapped pack and rewrites its commit-graph, so the…
Repacks a repo into one bitmapped pack and rewrites its commit-graph, so the next clone reuses the bitmap instead of walking the whole object graph.
POST /v1/git/repos/{name}/gc
| Address | https://api.hanzo.ai/v1/git/repos/{name}/gc |
| Method | POST |
| Operation | post_git_repos_by_name_gc |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Repacks a repo into one bitmapped pack and rewrites its commit-graph, so the next clone reuses the bitmap instead of walking the whole object graph. Idempotent, and safe to interrupt — git swaps both artifacts atomically. It runs under one pack slot with the same memory bounds as a clone, so it can block behind heavy pack traffic rather than compete with it. Storage usage is re-measured afterwards, since a repack reclaims space.
Request
1 field.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
name | path | string | yes | Name is the repo's org-unique handle, from the :name path segment. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | gcOut | ok |
200 body — 3 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
maintained | body | boolean | — | Maintained is always true; the call fails rather than reporting false. |
repo | body | string | — | Repo is the repo that was repacked. |
sizeBytes | body | integer | — | SizeBytes is the size measured AFTER the repack — usually smaller, since repacking drops the packs it supersedes. |
Failure carries the platform error shape — see Errors.
Examples
hanzo git repos gc <name>import { Configuration, GitApi } from 'hanzoai';
const api = new GitApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postGitReposByNameGc({ name: 'name' });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import GitApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = GitApi(client).post_git_repos_by_name_gc(name='name')cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.GitAPI.PostGitReposByNameGc(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, git_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = git_api::post_git_repos_by_name_gc(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.GitApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new GitApi(client).postGitReposByNameGc();curl -X POST https://api.hanzo.ai/v1/git/repos/<name>/gc \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches git through the git tool, which names its 56 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "get_git"
}
}
}'How is this guide?