Commercial CI/CD
Source provider setup
Connect GitHub, GitLab, Bitbucket, and Azure Repos with provider apps, repository sync, webhook events, checkout credentials, and status publishing.
GitHub
Install the GitHub App, return through the signed callback, sync repositories, and verify signed webhook deliveries and check runs. Stored inbound replay is implemented for GitHub deliveries.
GitLab, Bitbucket, Azure Repos
OAuth/provider-app flows and encrypted manual fallback credentials exist. Refresh/revocation details differ by provider; non-GitHub webhooks prefer organization-specific configured tokens with a provider-wide shared fallback. They are not body-signed, and stored replay is not implemented for those providers.
Status publishing
Provider status clients exist, but every provider must pass live canaries with real repositories and commits. OAuth canaries do not replace evidence for a complete browser callback, refresh, reconnect, and disconnect lifecycle.
Provider launch checklist
Validate repository sync pagination, push/PR/tag webhooks, checkout tokens, and status publishing. Changed-file filtering only uses paths present in the webhook payload; missing PR/MR file lists are not fetched. Validate GitHub replay separately, and review hosted versus self-hosted pull-request credential behavior before enabling untrusted contributions.