Git sync

Because every Orvanta script, flow, and app is a code artifact, a workspace can be connected to a Git repository. This is a Business or Enterprise capability, installed as a GitHub App on the repositories you want to sync.

There are two related but distinct mechanisms:

Deploy-triggered Git sync

A workspace can have one or more repositories configured under git_sync in workspace settings, with each repository’s filters (include_type, include_path, exclude_path, extra_include_path) controlling which deploys it tracks. When those are set up, every matching deploy of a script, flow, or app queues a background job intended to commit the deployed artifact to the linked branch — a one-way, workspace → Git flow that would track deploys as they happen without pulling changes made directly in Git back into the workspace.

To connect a repository:

1. Install the Orvanta GitHub App on the repository (or the whole org) from Instance settings.
2. In workspace settings, add the repository and configure which paths/types it should track.

Known gap

The commit step of deploy-triggered Git sync doesn’t currently run: the background job queued by a deploy fails before it reaches the repository, so no commit is produced. Repository and filter configuration is available and saved as normal, and the deploy itself still completes — only the push to Git is affected. To keep a Git repository in sync with a workspace today, use CLI-based sync below.

CLI-based sync (local files ↔ workspace)

Separately from the GitHub App integration above, the Orvanta CLI can push and pull between a local checkout and a workspace in either direction:

orvanta sync pull   # pull remote changes and apply them locally
orvanta sync push   # push local changes and apply them remotely

This is how most teams actually get Git in the loop day to day: keep the local checkout under normal Git version control, and use orvanta sync push/pull to move changes between that checkout and the workspace — reviewing changes as an ordinary pull request against the local files, independent of the deploy-triggered mechanism above.

Related

• Flows as artifacts: The artifacts that get committed.
• CLI: sync: the orvanta sync push/pull commands.
• Enterprise overview
• Self-hosting Overview