OpenapiGit
Binds a Slack channel to a repo, so the lifecycle notifier posts that repo's…
Binds a Slack channel to a repo, so the lifecycle notifier posts that repo's push and deploy events there. Answers 201.
POST /v1/git/repos/{name}/subscriptions
| Address | https://api.hanzo.ai/v1/git/repos/{name}/subscriptions |
| Method | POST |
| Operation | post_git_repos_by_name_subscriptions |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Binds a Slack channel to a repo, so the lifecycle notifier posts that repo's push and deploy events there. Answers 201. The same channel twice on one repo is a 409; a repo outside the caller's scope is a 404, exactly as reading it is.
Request
4 fields, body application/json (required).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
name | path | string | yes | Name is the repo to subscribe, from the :name path segment. |
channel | body | string | — | Channel is the Slack channel the notifier posts to — an id (C…/G…), a #name, or a bare name. |
events | body | string[] | — | Events narrows delivery to these lifecycle kinds (push.landed, deploy.live, deploy.failed). |
name | body | string | — | Name is the repo to subscribe, from the :name path segment. |
Response
| Status | Body | Meaning |
|---|---|---|
201 | subscriptionView | created |
201 body — 5 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
channel | body | string | — | Channel is the Slack channel id or name the notifier posts to. |
createdAt | body | string | — | CreatedAt is RFC 3339 UTC. |
events | body | string[] | — | Events is the kind filter; absent means every deliverable kind. |
id | body | string | — | ID is the subscription's identifier ("sub_…"), the handle to delete it by. |
repo | body | string | — | Repo is the repo whose lifecycle events are delivered. |
Failure carries the platform error shape — see Errors.
Examples
hanzo git repos subscriptions create <name>import { Configuration, GitApi } from 'hanzoai';
const api = new GitApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postGitReposByNameSubscriptions({ name: 'name', channel: "<channel>", events: ["<events>"] });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_subscriptions(name='name', channel="<channel>", events=["<events>"])cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.GitAPI.PostGitReposByNameSubscriptions(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_subscriptions(&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).postGitReposByNameSubscriptions();curl -X POST https://api.hanzo.ai/v1/git/repos/<name>/subscriptions \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"channel": "<channel>",
"events": [
"<events>"
]
}'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?