Skip to content
Gitdown Sync

Gitdown Sync

Back up GitHub repositories to Gitdown without giving up control of your Git history.
Get startedAPI reference

Gitdown Sync copies a GitHub repository’s portable Git history and Git LFS objects into a non-public Gitdown repository. Use it to keep a second remote or to try Gitdown without changing the workflow your team already uses.

What is available

Section titled “What is available”
  • One connection links one GitHub repository to one Gitdown repository.
  • Personal targets are Private; organization targets are Internal. Sync never creates a Public repository.
  • Branches, tags, reachable Git objects, and referenced Git LFS objects are in scope.
  • GitHub issues, pull requests, repository settings, refs/pull, Git notes, LFS locks, recursive submodules, and external .lfsconfig files are not copied.

Safety before convenience

Section titled “Safety before convenience”

Backup-only is the default workflow. Two-way writes require an explicit human choice. Sync never invents a merge: incompatible changes pause the affected ref and surface an incident so a human or authorized agent can choose the Git workflow that resolves it.

Continue with product setup and sign-in, compare backup-only and two-way modes, learn how conflicts and incidents preserve history, or review the security posture and import limits.