Documentation

Import and GitHub Sync

Import Git history, keep a GitHub fallback, and understand repository canonicality.

Upstream supports GitHub as an import, migration, mirror, or fallback path. A repository still has one canonical source of truth at a time.

Import from GitHub

Open Repositories, select Import repository, connect GitHub if needed, and choose the source repository and destination namespace.

The import moves Git history and refs into the Upstream repository model. It does not create a second Upstream identity or organization.

Canonicality

  • Upstream-canonical: Upstream owns the repository. GitHub may receive a one-way read-only mirror.
  • GitHub-canonical: GitHub remains authoritative while Upstream synchronizes the repository and related activity.

Upstream never treats both sides as writable co-equal authorities. That prevents conflicting pushes and ambiguous merge state.

GitHub Actions fallback

A synchronized or mirrored repository can use GitHub Actions as its Actions provider. This is useful for workflows that require GitHub-specific APIs or macOS and Windows runners while Native support is unavailable.

Before removing GitHub Sync, Upstream checks whether required workflows would lose an execution path.