hosting

PUT `/v1/sites/{siteId}/repo`

Connect (or re-connect) a repository to a site.

Kimlik Doğrulama

Bearer token olarak bir API anahtarı gönderin. Anahtar hosting.deploy.manage iznine sahip olmalıdır; bu izne sahip olmayan bir anahtar 404 ile değil, 403 ile reddedilir.

Bu uç nokta hiçbir organizasyon kimliği almaz. Anahtarınız zaten ait olduğu organizasyonu tanımlar ve yanıt bu organizasyonla sınırlandırılır.

Dene

Köşeli parantez içindeki her şeyi kendi değerlerinizle ve anahtar yer tutucusunu panonuzdan bir anahtarla değiştirin.

curl -X PUT https://api.zinndigital.com/v1/sites/{siteId}/repo \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "provider": <string>, "repo": <string> }'

Oturum açtınız mı? Panonuzdaki API konsolu, gerçek organizasyon kimliğinizi ve kendi anahtarınızı otomatik olarak doldurur ve isteği canlı API üzerinde çalıştırarak gerçek yanıtı görmenizi sağlar. Bu uç noktayı API konsolunda açın

Ayrıntılar

Confirms the repository exists on the connected account, stores the connection, and creates or updates the provider-side push webhook — and, when `build_mode` is `ci`, commits the Zinn® build workflow to the repository. The provider work happens before the row is reported as connected, so a hook that could not be created never leaves a row claiming it was. Requires `hosting.deploy.manage`.

Parametreler

Ad	Tür	Zorunlu	Ne olduğu
`siteId (path)`	`Uuid`	Evet	Site ID (UUIDv7).

İstek gövdesi

Ad	Tür	Zorunlu	Ne olduğu
`provider`	`string`	Evet	—
`owner`	`string`	Hayır	—
`repo`	`string`	Evet	—
`branch`	`string`	Hayır	—
`build_mode`	`BuildMode`	Hayır	How the published files are produced. `publish` serves the repository's own files — right for plain HTML and for a repo whose generator output is committed. `ci` runs the build…
`build_command`	`string`	Hayır	—
`output_dir`	`string`	Hayır	—
`publish_branch`	`string`	Hayır	—
`auto_deploy`	`boolean`	Hayır	—

Yanıt

Ad	Tür	Zorunlu	Ne olduğu
`site_id`	`Uuid`	Evet	UUIDv7 identifier — sortable by creation time (docs/02 §8).
`provider`	`string`	Evet	The git provider — `github` or `gitlab`. A machine identifier.
`owner`	`string`	Evet	The account or namespace the repository lives under.
`repo`	`string`	Evet	—
`full_name`	`string`	Evet	`owner/repo`, or just the repo when the account owns its namespace.
`branch`	`string`	Evet	The branch a push deploys from.
`build_mode`	`BuildMode`	Evet	How the published files are produced. `publish` serves the repository's own files — right for plain HTML and for a repo whose generator output is committed. `ci` runs the build…
`build_command`	`string`	Evet	Blank in `publish` mode — a stored command nothing runs would read as a build.
`output_dir`	`string`	Evet	Which directory is published. Blank means the repository root.
`publish_branch`	`string`	Evet	Where CI commits the built output in `ci` mode.
`auto_deploy`	`boolean`	Evet	Whether a push deploys automatically. Off still records every delivery, so a customer can watch pushes arriving before letting us act on them.
`webhook_url`	`string`	Evet	The URL the provider was told to deliver to. Computed, never stored — a stored copy would keep naming the origin that was current when the row was written. Blank on an environme…
`webhook_registered`	`boolean`	Evet	Whether a provider-side hook actually exists. False here with a connection present means pushes are NOT being watched.
`last_delivery_at`	`object`	Evet	When the provider last delivered anything, or null for NEVER. Null is the single most useful diagnostic on this screen: "connected but never delivered" is what a mis-scoped toke…
`last_delivery_note`	`string`	Evet	What we did with the last delivery, including when we ignored it. Written for every delivery, because "never delivered" and "delivering, ignored" are different problems with dif…
`connected_account`	`string`	Evet	The label of the credential connection this repository is read with.

Bu uç noktanın dönderebileceği hatalar

401 · 403 · 404 · 422 · 429

PUT /v1/sites/{siteId}/repo