Connect a git repository
Attach a repository to your Wizata tenant, register the key, and enable git.
Connecting a repository happens in two steps. Wizata generates a key first and only enables git once that key works — so a mistyped URL or an unregistered key leaves your existing pipelines untouched rather than half-migrated.
Step 1 — Attach the repository
Go to Settings → Git Repository and provide:
Attach is unavailable? Git Repository Sync is a licensed option, activated on demand for Professional and Enterprise plans. When it is not active on your environment the Attach button is disabled and the page says Git as repository is not part of this environment's license. See Licensing and contact Wizata to enable it — nothing else on this page will work until then.
| Field | Notes |
|---|---|
| Repository URL | The SSH remote. HTTPS URLs are rejected. |
| Provider | GitHub, GitLab, Azure DevOps, Bitbucket, or generic. |
| Default branch | Usually main or master. |
The URL must be the SSH form:
GitHub [email protected]:team/pipelines.git
GitLab [email protected]:team/pipelines.git
Azure DevOps [email protected]:v3/org/project/repo
Bitbucket [email protected]:workspace/pipelines.git
Self-hosted ssh://[email protected]:2224/team/pipelines.git
On most providers you can copy this from the Clone button by choosing SSH.
When you save, Wizata generates an SSH keypair and displays the public key. The private half never leaves the platform.
Step 2 — Register the key
Copy the public key and register it with your provider. Where it goes depends on the provider — on Azure DevOps and Bitbucket the obvious place is the wrong one, so follow Provider setup and requirements.
Wizata shows the correct instructions for your provider alongside the key, including a warning when the key will carry more access than the single repository.
Make sure the key has write access. Wizata pushes on every pipeline save, and a read-only key produces a connection that looks healthy and fails at the first edit.
Step 3 — Check the status
Back in Wizata, the connection status tells you where you are:
| Status | Meaning |
|---|---|
connected | The repository is reachable and the key is accepted. |
auth_failed | The key is not registered yet, or was registered in the wrong place. |
host_verification_failed | The host key does not match what was recorded at attach time. |
unreachable | DNS, network or firewall — the host did not answer. |
auth_failed is expected until you complete step 2. The message tells you where the key belongs for your provider.
Step 4 — Enable git
Once the status is connected, enable git for the tenant. Wizata then:
- creates an initial commit if the repository is empty;
- migrates your existing pipelines into it;
- switches all reads and writes over to the repository.
From this point every pipeline save is a commit.
Disconnecting
Detaching stops Wizata using the repository. Your pipelines are migrated back into the platform first, and the repository is left exactly as it is — Wizata never deletes it.
Detaching needs the same licensed option as attaching. If Git Repository Sync has been removed from your license while a repository is connected, your pipelines keep working from the repository; ask Wizata to detach it for you.
After detaching, revoke the deploy key with your provider. It is no longer used, and leaving it registered leaves a credential in place with nothing needing it.
Updated 20 days ago