Proposes a branch for merging and returns it with its number.
Proposes a branch for merging and returns it with its number. Answers 201.
POST /v1/git/repos/{name}/pulls
| Address | https://api.hanzo.ai/v1/git/repos/{name}/pulls |
| Method | POST |
| Operation | post_git_repos_by_name_pulls |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Proposes a branch for merging and returns it with its number. Answers 201. Both branches must already exist — a proposal naming a branch nobody pushed is a typo, not a plan — and base defaults to the repo's default branch.
Proposing the same head into the same base twice is a 409 while the first proposal is still open, so a retried agent run leaves ONE thing to review rather than a pile of identical ones. A repo outside the caller's scope is a 404, exactly as reading it is.
Request
6 fields, body application/json (required).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
name | path | string | yes | Name is the repo the proposal belongs to, from the :name path segment. |
base | body | string | — | Base is the branch the work is proposed INTO, by short name. |
body | body | string | — | Body is the longer description. |
head | body | string | — | Head is the branch holding the work, by short name (agent/fix-503). |
name | body | string | — | Name is the repo the proposal belongs to, from the :name path segment. |
title | body | string | — | Title is the one-line summary of what is being proposed. |
Response
| Status | Body | Meaning |
|---|---|---|
201 | pullView | created |
201 body — 11 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
author | body | string | — | Author is the user who opened it; empty for a caller with no user. |
base | body | string | — | Base is the branch the work is proposed into. |
body | body | string | — | Body is the longer description; empty when none was given. |
createdAt | body | string | — | CreatedAt is RFC 3339 UTC. |
head | body | string | — | Head is the branch holding the work. |
mergedRev | body | string | — | MergedRev is what base points at now that the merge landed. |
number | body | integer | — | Number is the proposal's per-repo handle, dense from 1. |
repo | body | string | — | Repo is the repository the proposal belongs to. |
state | body | string | — | State is "open" or "merged". |
title | body | string | — | Title is the one-line summary. |
updatedAt | body | string | — | UpdatedAt is RFC 3339 UTC. |
Failure carries the platform error shape — see Errors.
Examples
hanzo git repos pulls create <name>import { Configuration, GitApi } from 'hanzoai';
const api = new GitApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postGitReposByNamePulls({ name: 'name', base: "<base>", body: "<body>" });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_pulls(name='name', base="<base>", body="<body>")cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.GitAPI.PostGitReposByNamePulls(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_pulls(&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).postGitReposByNamePulls();curl -X POST https://api.hanzo.ai/v1/git/repos/<name>/pulls \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"base": "<base>",
"body": "<body>"
}'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?