Advanced / user manual
Git Integrations
Connects Git credentials, providers, and repository sources. Stores encrypted credentials, validates provider tokens live, links repositories, and installs auto-deploy webhooks on provider-token sources.
Coordinate deployments, traffic, scaling, security, and provider integrations.
Git source to deployment flow
Forge control plane and provider APIs
How to use it
Operator workflow
- 01
Add a credential (SSH key or HTTPS token) or connect a provider account with a personal access token.
- 02
Test the token before saving — validation calls the provider API, not a local guess.
- 03
Link the repository, choosing public, credential, or provider-token mode.
- 04
Enable auto-deploy only on provider-token sources so the webhook installs; verify the secret and ID.
What Forge owns
Boundary and safety
Secrets stay server-side encrypted. Webhooks install only on provider-token sources.
Review the affected node, workload, route, or secret before saving. Capture state and health evidence before changes that affect data or public traffic.
Before you finish
Verification checklist
- Token test passes.
- Source shows provider and branch.
- Auto-deploy sources show a webhook ID.
- Credential-linked sources show the no-webhook warning.
Continue the manual
Use this feature in the wider Forge workflow.
Move from platform understanding to the relevant operating guide when you need exact environment, network, deployment, or recovery steps.