On this page
Other Git Providers
The Other Git Providers option is a manual, HTTPS-only connection for any git server that Temps doesn't integrate with natively — Azure DevOps, Gogs, SourceHut, AWS CodeCommit, Bitbucket Data Center, or your own self-hosted server. Start from Connect a Git Provider if you haven't opened the Git Providers page yet.
Connect a generic repository
- On the Add Git Provider screen, choose Other Git Providers.
- Choose the mode:
- Public repository — paste the HTTPS clone URL (e.g.
https://git.example.com/acme/app.git) and click Connect. No credentials needed. - Private (HTTPS token) — paste the HTTPS clone URL and an access token. Optionally set a token username (defaults to
x-access-token, which works for most providers; Azure DevOps and some hosts expect a specific value). Click Connect.
- Public repository — paste the HTTPS clone URL (e.g.
- After connecting, Temps shows a webhook URL. Add it in your git server's webhook settings (pointing at push events) to enable automatic deploys on push.
Only HTTPS clone URLs are supported — SSH is not. You can also trigger deploys for these providers from CI or the API instead of a webhook.
Limitations
A generic connection clones and deploys, but unlike the native integrations:
- There is no repository browser — you enter the clone URL directly.
- There are no pull-request comments.
- The webhook is not registered automatically — you add the shown webhook URL to your git server yourself.
If your provider is GitHub, GitLab, Bitbucket Cloud, or Gitea, prefer the dedicated guide instead — those give you a repository browser and an auto-registered webhook.
Once connected, confirm the status shows Active on the Git Providers page. There is no repository browser for a generic connection — the project uses the clone URL you entered here. Continue with Deploy a Project.