repo-rebase(1)

Usage

repo rebase {[<project> ...] | -i <project> ...}

Overview

Summary

Rebase local branches on upstream branch

Options

-h, --help: show this help message and exit

--fail-fast: stop rebasing after first error is hit

-f, --force-rebase: pass --force-rebase to git rebase

--no-ff: pass --no-ff to git rebase

--autosquash: pass --autosquash to git rebase

--whitespace=WS: pass --whitespace to git rebase

--auto-stash: stash local modifications before starting

-m, --onto-manifest: rebase onto the manifest version instead of upstream HEAD (this helps to make sure the local tree stays consistent if you previously synced to a manifest)

Logging options:

-v, --verbose: show all output

-q, --quiet: only show errors

-i, --interactive: interactive rebase (single project only)

Multi-manifest options:

--outer-manifest: operate starting at the outermost manifest

--no-outer-manifest: do not operate on outer manifests

--this-manifest-only: only operate on this (sub)manifest

--no-this-manifest-only, --all-manifests: operate on this manifest and its submanifests

Run `repo help rebase` to view the detailed manual.

Details

'repo rebase' uses git rebase to move local changes in the current topic branch to the HEAD of the upstream history, useful when you have made commits in a topic branch but need to incorporate new upstream changes "underneath" them.

History

Arch Linux 2026-11-01: the text shown here
Debian 13 (Trixie) to Debian 12 (Bookworm)
Debian 11 (Bullseye)

--all-manifests since Debian 12 (Bookworm); --no-outer-manifest since Debian 12 (Bookworm); --no-this-manifest-only since Debian 12 (Bookworm); --outer-manifest since Debian 12 (Bookworm); --this-manifest-only since Debian 12 (Bookworm).