Skip to main content
A skill can live in its own git repo and release via CI instead of (or alongside) the drafts workflow. A tenant admin must first register the skill id + repo via POST /api/v1/tenants/{tenantId}/repo-links.
A repo link can restrict which branches may release via releaseBranches (empty = no restriction). Because a git tag isn’t reliably “on” one branch, the OIDC path proves the branch through the workflow job’s environment: claim, checked against GitHub’s own environment deployment policy — not something this platform tries to derive itself. The PAT path takes --release-branch at face value: a weaker, unverified guarantee, consistent with PAT being the fallback auth path throughout.