Back up GitHub, GitLab, Bitbucket, and Forgejo repositories with gitbackup

Back up GitHub, GitLab, Bitbucket, and Forgejo repositories with gitbackup

Run repeatable cross-forge repository backup jobs from one config instead of hand-scripting clone and export steps per provider.

Prerequisites

gitbackup binary or container image, forge access tokens, backup storage

Installation

Use the upstream install or setup path that matches your environment:

• Docker images are published to GitHub Container Registry on every release:
• docker pull ghcr.io/amitsaha/gitbackup:
• docker run --rm \
• Docker Desktop for Mac runs containers inside a Linux VM and translates volume mounts through its filesystem layer (VirtioFS). Because of this translation, the container UID (65532) is mapped automatically — you do **...

Requirements and caveats from upstream:

• Docker image

• Docker image

• The container runs as a non-root user (nonroot, UID 65532). HTTPS cloning (-use-https-clone) is recommended inside containers because it requires no SSH key management.

Basic usage or getting-started notes:

• Run with HTTPS cloning (recommended):

• Starting with the 0.6 release, if you run gitbackup without specifying GITHUB_TOKEN, it will prompt you to complete

• Source: https://github.com/amitsaha/gitbackup

• Extracted from upstream docs: https://raw.githubusercontent.com/amitsaha/gitbackup/HEAD/README.md

Documentation

• https://github.com/amitsaha/gitbackup

Source

• Agent Skill Exchange