Fork2Self Autor: Joyrida12

Beta software. Fork2Self is functional and in active use, but rough edges are expected. Migrations can fail in surprising ways depending on the destination forge's version, the source repo's quirks, and rate limits at either end. Configuration and storage formats may still change between versions without a migration path. Please report issues on the GitHub tracker.

Claude Code wrote all of this

Fork2Self adds a one-click "Fork to…" action to your browser. When you're on a recognized repository page on GitHub, GitLab, Gitea/Forgejo, Gogs, OneDev, GitBucket, or Bitbucket Cloud, click the toolbar button (or use the right-click context menu) to mirror that repository into a self-hosted Git instance you control.

The cloning happens server-to-server through your destination forge's native migration API. Your browser sends one request; the destination handles the rest. No data passes throug

Quick start

1. Open the extension's options page and add a destination — pick Gitea/Forgejo or GitLab, paste the base URL, and provide a personal access token. Grant host permission for that origin when prompted.
2. Browse to a repository on a supported source.
3. Click the toolbar icon, or right-click and choose "Fork to…". The migration starts immediately and lands in the popup's History tab.

Supported sources

• GitHub
• GitLab (gitlab.com and self-hosted)
• Gitea / Forgejo (including Codeberg)
• Gogs
• OneDev
• GitBucket
• Bitbucket Cloud
• Generic Git URL via the custom-hostname mapping
  ## Supported destinations
• Gitea / Forgejo: full content migration with optional pull-mirror. - GitLab CE / EE: code-only via import_url. P

Features

• One-click forking from the toolbar popup or the right-click "Fork to…" menu.
• Multiple destinations: configure several self-hosted instances; one is the default for one-click flows, the rest sit in a subm- Optional content migration: wiki, issues, pull re milestones — toggled per fork by what the source and destination both support.
• Pull-mirror mode keeps your fork in sync with upstream automatically (on backends that support it). - Private source repo support via per-host personal
• Custom hostname mapping for self-hosted source instances (e.g. an internal GitLab at git.example.lan).
• Migration history with the last 50 attempts. Failed migrations get a manual "Delete repo" button that calls the destination's delete API.
• Automatic cleanup of partial repos on rate-limit failures (Gitea).

Privacy

• No telemetry, no analytics, no remote configuration.
• Network requests go only to (a) the source repo ytination forge you've configured.
• Tokens are stored in the browser's local extensiod or transmitted elsewhere.
  collection_permissions: ["none"]`.

Permissions

• storage — persist destinations, tokens, and migration history locally.
• contextMenus — the "Fork to…" right-click entries.
• notifications — toast on fork start, success, a
• activeTab — read the URL of the tab the action was clicked on, to detect the source repo.
• Host permissions are NOT requested by default. The extension asks for permission to reach a specific destination origin only when
  you add or test that destination in the settings fl

Open source

GPL-3.0-only. Homepage: <https://rickygrassmuck.github.io/Fork2Self/> · Source: <https://github.com/RickyGrassmuck/Fork2Self>