Replace pages
Sets or clears the custom domain (cname) and updates HTTPS enforcement, build type, or source.
PUT /v1/provider/github/repos/{repo}/pages
| Address | https://api.hanzo.ai/v1/provider/github/repos/{repo}/pages |
| Method | PUT |
| Operation | put_provider_github_repos_by_repo_pages |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Sets or clears the custom domain (cname) and updates HTTPS enforcement, build type, or source. ONLY the provided fields are sent to GitHub, so an update never resets a setting the caller did not mention.
Request
7 fields, body application/json (required).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
repo | path | string | yes | Repo is the repository, from the :repo path segment. |
branch | body | string | — | Branch switches the legacy source branch. |
buildType | body | string | — | BuildType switches the builder: "legacy" or "workflow". |
cname | body | string | — | CNAME is the custom domain. |
httpsEnforced | body | boolean | — | HTTPSEnforced toggles GitHub's enforce-HTTPS bit. |
path | body | string | — | Path is the source directory to pair with Branch: "/" (the default) or "/docs". |
repo | body | string | — | Repo is the repository, from the :repo path segment. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | provider.githubPagesUpdatedOut | ok |
default | problem-details | refused |
200 body — 2 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
repo | body | string | — | Repo is the repository that was updated. |
updated | body | boolean | — | Updated is always true — a failure is an HTTP error, never this shape. |
Failure carries the platform error shape — see Errors.
Examples
hanzo provider github repos pages replace <repo>import { Configuration, ProviderApi } from 'hanzoai';
const api = new ProviderApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.putProviderGithubReposByRepoPages({ repo: 'repo', branch: "<branch>", buildType: "<buildType>" });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import ProviderApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ProviderApi(client).put_provider_github_repos_by_repo_pages(repo='repo', branch="<branch>", build_type="<buildType>")cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)
resp, _, err := client.ProviderAPI.PutProviderGithubReposByRepoPages(context.Background()).Execute()
if err != nil {
return err
}use hanzo_client::apis::{configuration::Configuration, provider_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = provider_api::put_provider_github_repos_by_repo_pages(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.ProviderApi;
ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));
var result = new ProviderApi(client).putProviderGithubReposByRepoPages();The method above is the one at the current release of the document. [email protected] (npm) was generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl -X PUT https://api.hanzo.ai/v1/provider/github/repos/<repo>/pages \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"branch": "<branch>",
"buildType": "<buildType>"
}'MCP declares no tool for provider — tools/list on https://api.hanzo.ai/v1/mcp names the products it does reach. Use HTTP or an SDK.
How is this guide?