Git integration

When git integration is enabled, your pipeline definitions are stored as JSON files in a git repository that you own, instead of inside the Wizata platform.

📘

A licensed option. Git Repository Sync is available on demand for Professional and Enterprise plans and is activated per environment by Wizata, because it comes with dedicated storage. If the option is not active on your environment, the Attach and Detach actions in Settings → Git Repository are unavailable and say so. See Licensing and contact us to enable it.

You still build pipelines from the AI Lab in the usual way, and every save becomes a commit — so you get history, diffs, review and rollback from your existing tooling.

One thing does change in the AI Lab itself: a pipeline gains a published version and drafts, and the pipeline header gains a branch selector to move between them. Editing no longer changes what production runs until you publish. Drafts and publishing covers that from the pipeline screen; How Wizata uses branches covers what it looks like in the repository.

What this gives you

• A full history of every pipeline change, with the author and timestamp of each edit.
• Review before production, using the branch and merge tools your team already has.
• Recovery, because a pipeline deleted by mistake is still in the repository history.
• Portability, since the definitions are plain JSON in your own repository.

What Wizata stores there

pipelines/<key>.json     your pipeline definitions
scripts/                 your python scripts
.wizata/                 reserved for platform metadata
README.md                created by Wizata when the repository is first set up

Models and other large binary artefacts are not stored in git — they stay in the platform's object storage.

Before you start

You will need:

• the Git Repository Sync option active on your environment — on demand for Professional and Enterprise plans, see Licensing;
• an empty repository on a supported provider (GitHub, GitLab, Azure DevOps or Bitbucket);
• permission to register an SSH key on it, or on the account that owns it;
• the Administrator role in Wizata.

📘

The repository can be empty. Wizata creates the initial commit and folder layout for you.

Wizata generates the SSH key itself — you never paste a private key into the platform. You register the public key with your provider, and Wizata pushes and pulls with it from then on.

Where that key has to be registered differs by provider, and getting it wrong is the most common reason a connection fails. Read Provider setup and requirements for your provider before you begin.