Source control
A source-control (SCM) provider is how GantryCD talks to your Git platform. A single provider handles the whole relationship:
- Webhooks — verify and normalize deliveries into provider-neutral events (a push, a pull-request change) that drive deployments.
- Clone credentials — mint short-lived credentials so a runner can clone the repo, without storing a long-lived token on the stack.
- Pull-request projection — fetch PR metadata so GantryCD can post preview plans and track state.
| Provider | Status |
|---|---|
| GitHub App | Supported |
Adding another platform (GitLab, Bitbucket, …) is an extension point — the durable webhook inbox, PR projection, and push-triggered deployments downstream are all provider-agnostic.
Day-to-day
Connecting a specific repository to a stack — and what automatic plans you get on push and PR — is covered in Connecting repositories.
Internals
The webhook contract, the durable inbox, and PR refresh are in SCM And Pull Requests.