Skip to main content

​
Git Sync and Workspace Repositories

Git Sync connects a platform workspace to a GitHub workspace repository. The platform reads rollout code and configuration from that repository, discovers rollouts under rollouts/, and makes them available for training. Your local workspace directory is a clone of the same repository. Push to any branch to sync its rollout catalog.

​
Repository Setup

1

Create or connect a workspace repository

Workspace owners and admins connect GitHub in the platform, then create a private workspace repository from the Osmosis workspace template or connect an existing repository.New repositories created from the platform include the starter examples multiply-local-strands, multiply-local-openai, and multiply-harbor-strands. For the full first-time setup flow, start with Onboarding.
2

Work from the local workspace directory

Your local workspace directory should be a clone of the connected GitHub repository. Invited members use the existing workspace repository rather than creating a second one.
3

Verify local context

From your local workspace directory, confirm the origin remote points at the connected GitHub repository:

​
How Sync Works

  • Pushing to any branch triggers an automatic sync for that branch.
  • The platform discovers rollout definitions in the rollouts/ directory independently for each branch.
  • Each rollout subdirectory (e.g. rollouts/my-rollout/) becomes a rollout entity on the platform, available for training and evaluation.
  • Config files under configs/ are also synced so that osmosis train submit can reference them by path.
  • The platform records sync history with branch, commit SHA, author, message, status, and number of rollouts discovered.
  • Deleting a branch removes that branch’s rollout catalog without removing rollouts that still exist on another branch.
Git Sync is the source of truth for your rollout code. The CLI reads config values from the local TOML file you pass, but rollout code comes from the synced workspace repository. Commit and push before submitting code changes. Set branch to use a pushed branch or commit_sha for a specific pushed revision; omit both to use the default branch.

​
Sync Status

View sync history in the platform under Git Integration. Each sync event shows: A manual sync action is available in the platform to re-process every repository branch without pushing a new commit.

​
Blocking States

The platform shows a banner when GitHub setup blocks training workflows.

​
Important Notes

  • Every branch is synced automatically; there is no per-workspace branch-sync setting.
  • The Rollouts page has a branch picker. The repository default branch is selected first, and ?branch=<name> preserves the selection in the URL.
  • If the repository is renamed on GitHub, update your local origin remote and check the platform connection.
Use branch in a run config to follow a branch, or commit_sha to pin a specific commit. They are mutually exclusive; omit both to use the default branch.

​
Next Steps

Workspace Repository

Learn how local CLI commands are scoped to a repository.

Training

Submit and manage training runs after Git Sync succeeds.
Last modified on August 10, 2026