REPO(1)
π
REPO(1) β the repo rebase manual, bestie edition
okay so this is the manual for repo rebase, from the Repo Manual. yes it's giving very "let me move your commits around while you watch" energy. let's go π«Ά
β¨ SYNOPSIS β¨
repo rebase {[<project>...] | -i <project>...}
so like... either you name a bunch of projects, or you go -i mode with exactly one. pick your fighter π
πΈ DESCRIPTION πΈ
Summary
Rebase local branches on upstream branch. that's it, that's the whole vibe check. π¦
π OPTIONS π
-h,--helpβ show this help message and exit. the classic "wait what does this do again" button, no shame in it π--fail-fastβ stop rebasing after first error is hit. one oopsie and we're OUT, no cap π-f,--force-rebaseβ pass--force-rebasetogit rebase--no-ffβ pass--no-fftogit rebase--autosquashβ pass--autosquashtogit rebase--whitespace=WSβ pass--whitespacetogit rebase. note the=WS, you gotta give it a value bestie, it's not optional π--auto-stashβ stash local modifications before starting. your messy little uncommitted edits get tucked away first β¨-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). lowkey the responsible choice if you synced to a manifest before π
π Logging options:
-v,--verboseβ show all output. every last crumb, we love a chatty queen π-q,--quietβ only show errors. silent mode, main character energy, no commentary π-i,--interactiveβ interactive rebase (single project only). literally read that parenthetical, it's one project only okay?? don't try it with a whole list π
π§ 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. (yes there's a whole deep-dive version, go read it if you want the extended cut π)
π₯ 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.
so basically: you built your cute little tower of commits, upstream moved, and now you gotta slide your tower on top of the new stuff. it's giving "scoot over bestie" π β¨
and that's the whole page!! π this was repo rebase from the Repo Manual, dated June 2026. periodt, go rebase something π
π¦ where this page comes from
- arch rolling: repo 2.67-1 Β· Apache-2.0
- fedora 43: repo 2.68-1.fc43
- fedora 43: repo 2.69-1.fc43 Β· Apache-2.0
- fedora 44: repo 2.68-1.fc44
- fedora 44: repo 2.69-1.fc44 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms