Docs

Get started

Install the CLI, then clone any repo hosted on ripclone.com. No account is needed to clone.

Linux and macOS, x86-64 and arm64. Editable clones need git on the PATH. The clone is a normal git repo: git pull and git push go to GitHub with your own credentials.

Clone modes

• ripclone clone owner/repo: full history, the same result as git clone.
• --depth 1: only the latest commit. Best for CI and agents that run git.
• --mode files: the working tree, no .git. Fastest.

All flags are in the CLI reference. Exit codes for scripts are in the same place.

Add a repo

Sign in with GitHub on the Repos page and enter owner/name, or from a terminal:

ripclone.com hosts public GitHub repos up to 2 GB, or up to 10 GB with 500 or more stars. Adding starts the first build; the repo page shows its progress. Once added, a repo is public on ripclone.com for everyone.

CI and agents

Public clones work without a token. To add repos or build a specific commit from CI, create a token in Settings and set it as RIPCLONE_SERVER_TOKEN. In GitHub Actions:

- name: Clone with ripclone
  env:
    RIPCLONE_SERVER_TOKEN: ${{ secrets.RIPCLONE_TOKEN }}  # optional for public repos
  run: |
    curl -fsSL https://ripclone.com/install.sh | sh
    ripclone clone oven-sh/bun --depth 1

For agents, set RIPCLONE_AGENT=1: depth 1 becomes the default and prompts are off. Use --mode files when the agent never runs git.

Freshness

ripclone.com checks each hosted repo for new commits on its default branch every few minutes and builds them. A full clone of a branch whose newest commit is still building installs the previous build and fetches the rest from GitHub with your own git, so it never waits long. A depth-1 clone waits for its commit. Details: Freshness.

Self-host

The ripclone server is open source and needs no account. Run one for private repos, other git hosts, or your own storage. Start with the quick start, then storage, providers and webhooks. Point the CLI at it with RIPCLONE_SERVER.