Use cases
Where repo-bridge fits
One-way, repo-to-repo delivery as clean pull requests. No fork, no shared history, no leaked commits. Here are the workflows it was built for.
Agency → Client handoff
The problem. You build in your own repo with internal tooling, draft commits, and team chatter in messages. The client only needs the finished work.
With repo-bridge. Sync each release into the client's repo as a clean PR on a fresh branch. No internal history, no force-push, no shared git ancestry.
Whitelabel / multi-tenant delivery
The problem. One core product needs to land in many customer repos, each with its own path mappings, reviewers, and branch protection.
With repo-bridge. Configure one source repo and many destinations. Each sync opens a per-customer PR with an AI summary so their reviewers can ship quickly, all tracked in one fleet view.
Contractor → Enterprise repo
The problem. The enterprise repo is locked down: required reviewers, branch protection, and no outside collaborators with write access to main.
With repo-bridge. Repo Bridge installs as a GitHub App on the destination, opens PRs from a fresh branch, and keeps your working repo entirely separate. Note: destinations that require GPG-signed commits on the target branch aren't supported yet — sync to an unprotected staging branch and have the client's CI re-sign on merge.
Monorepo → product repo extraction
The problem. You develop in a monorepo but ship a standalone product repo for releases, distribution, or partner access.
With repo-bridge. Map only the paths that belong to that product. Each sync produces a release-ready PR in the standalone repo with drift detection between syncs. Delivered as a snapshot PR — not a rewritten git history.
Cross-team review boundary
The problem. Two codebases must stay separate — different teams, different access, different risk profiles — but changes still need to flow one way with a paper trail.
With repo-bridge. Every cross-boundary change becomes a reviewed PR with an AI summary, a stamped baseline, and a logged sync record you can point back to later.
Sound like your workflow?
Wire up a source and a destination repo, install the GitHub App, and open your first cross-repo PR in a few minutes.
Create a workspace