hosting

PUT /v1/sites/{siteId}/repo

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

Vituo vyote vya hosting

Uthibitishaji

Tuma ufunguo wa API kama tokeni ya kubeba. Ufunguo lazima uwe na ruhusa ya hosting.deploy.manage; ufunguo usio nayo unakataliwa kwa 403, si 404.

Endpoint hii haichukui kitambulisho cha shirika. Ufunguo wako tayari unalitambua shirika linalohusika, na jibu limewekewa kikomo kwa shirika hilo pekee.

Jaribu

Badilisha chochote kilicho ndani ya mabano ya pembe na maadili yako mwenyewe, na kishikiliaji cha ufunguo na ufunguo kutoka kwa dashibodi yako.

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> }'

Umeingia kwenye akaunti? Dashibodi yako ya kiweko cha API inajaza kitambulisho chako halisi cha shirika na ufunguo wako mwenyewe, na kuendesha ombi dhidi ya API ya moja kwa moja ili uweze kuona jibu halisi. Fungua sehemu hii ya mwisho (endpoint) kwenye konsole ya API

Maelezo

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`.

Vigezo

JinaAinaInayohitajikaKilicho hiki
siteId (path)UuidNdiyoSite ID (UUIDv7).

Mwili wa ombi

JinaAinaInayohitajikaKilicho hiki
providerstringNdiyo
ownerstringHapana
repostringNdiyo
branchstringHapana
build_modeBuildModeHapanaHow 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_commandstringHapana
output_dirstringHapana
publish_branchstringHapana
auto_deploybooleanHapana

Majibu

JinaAinaInayohitajikaKilicho hiki
site_idUuidNdiyoUUIDv7 identifier — sortable by creation time (docs/02 §8).
providerstringNdiyoThe git provider — `github` or `gitlab`. A machine identifier.
ownerstringNdiyoThe account or namespace the repository lives under.
repostringNdiyo
full_namestringNdiyo`owner/repo`, or just the repo when the account owns its namespace.
branchstringNdiyoThe branch a push deploys from.
build_modeBuildModeNdiyoHow 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_commandstringNdiyoBlank in `publish` mode — a stored command nothing runs would read as a build.
output_dirstringNdiyoWhich directory is published. Blank means the repository root.
publish_branchstringNdiyoWhere CI commits the built output in `ci` mode.
auto_deploybooleanNdiyoWhether a push deploys automatically. Off still records every delivery, so a customer can watch pushes arriving before letting us act on them.
webhook_urlstringNdiyoThe 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_registeredbooleanNdiyoWhether a provider-side hook actually exists. False here with a connection present means pushes are NOT being watched.
last_delivery_atobjectNdiyoWhen 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_notestringNdiyoWhat 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_accountstringNdiyoThe label of the credential connection this repository is read with.

Hitilafu ambazo mwisho huu unaweza kurudisha

401 · 403 · 404 · 422 · 429