Mirror the workspace's Git repository to a GitHub, GitLab, Gitea or Azure DevOps remote, and pull changes made there back into Talon.
Git remote
Every workspace already has its own Git repository inside Talon. Talon Connect → Source Control (/connect/source-control) mirrors it to a remote your team maintains — GitHub, GitLab, Gitea or Azure DevOps — for external collaboration and CI/CD, rather than keeping detections in a store only Talon can see.
Repository URL (HTTPS)
For example https://github.com/org/detections.git.
Branch
The remote branch to mirror to, main by default.
Access token
Encrypted at rest and never returned by the API. Use a fine-grained personal access token scoped to that one repository with Contents read/write (ghp_… on GitHub, glpat-… on GitLab).
Auto-push on merge
Push to the remote automatically whenever a change request merges.
Enable pull
Allow remote changes to flow back into the workspace. Also reveals the webhook settings.
Test connection checks the URL and token before you Save.
With Enable pull on, an optional push webhook makes the remote trigger a pull on every push (GitHub, GitLab and Gitea). Copy the payload URL (/api/workspaces/<id>/remote-repo/webhook) and click Generate secret; the secret is shown once, and Regenerate secret rotates it. Azure DevOps webhook signatures are not verified, so protect that endpoint at the network level instead.
Disconnect removes only Talon's remote configuration; the remote repository and its history are untouched.
Talon Connect → Source Control
The remote configuration panel. Fill in the repository URL, branch and token, click Test connection to verify before saving, and set Auto-push on merge and Enable pull independently.
Push, pull & status
The connected remote's card shows the provider, remote URL and branch, whether auto-push and pull are on, when it last synced, and a status: Synced, Conflict, Failed (with the error) or Not synced. Push mirrors the workspace's local main to the remote branch; Pull (when enabled) fast-forwards local from the remote.
If the remote has commits Talon doesn't, a push is refused and Talon offers Force push, which overwrites the remote branch.
If the histories have diverged, a pull reports a conflict — it is never auto-merged — and Talon offers Force pull, which discards local commits that are not on the remote.
Tip
Point the remote at a dedicated, empty detections repository, not a shared monorepo. Push mirrors the workspace's whole main, so a remote with history of its own turns your first push into a force-push decision.