REPO(1)

✨ NAME ✨

repo — bestie, this is the manual page for repo status 💖

---

🌸 SYNOPSIS 🌸

repo status [<project>...]

---

🎀 DESCRIPTION 🎀

💅 Summary

Show the working tree status — that's it, that's the vibe check 🦋

---

✨ OPTIONS ✨

• -h, --help — pops up this very help message and then dips, that's it, that's all 🫶
• -j JOBS, --jobs=JOBS — how many jobs you wanna run in parallel (default: it's giving "however many CPU cores you got" 👑)
• -o, --orphans — also show objects chillin' in the working directory that live outside of repo projects 🐣

📋 Logging options

• -v, --verbose — show ALL the output, no secrets, no crumbs left behind 💀
• -q, --quiet — only show errors. silent mode, mysterious mode, main character mode 🤫

🌈 Multi-manifest options

• --outer-manifest — operate starting at the outermost manifest 🧅
• --no-outer-manifest — do NOT operate on outer manifests, we said what we said 🙅‍♀️
• --this-manifest-only — only operate on this (sub)manifest 🎯
• --no-this-manifest-only, --all-manifests — operate on this manifest AND all its submanifests, the whole family reunion 🌳

Run repo help status to view the detailed manual. 👀

---

🔥 DETAILS 🔥

repo status compares the working tree to the staging area (aka index), and the most recent commit on this branch (HEAD), in each project specified. A summary is displayed, one line per file where there is a difference between these three states. Three states, one line each, we love a tidy lil comparison 💖

The -j/--jobs option can be used to run multiple status queries in parallel. Parallel go brrr ⚡

The -o/--orphans option can be used to show objects that are in the working directory, but not associated with a repo project. This includes unmanaged top-level files and directories, but also includes deeper items. For example, if dir/subdir/proj1 and dir/subdir/proj2 are repo projects, dir/subdir/proj3 will be shown if it is not known to repo. Like, we're snitching on the stray folders ngl 🕵️‍♀️

🦋 Status Display

The status display is organized into three columns of information, for example if the file subcmds/status.py is modified in the project repo on branch devwork:

project repo/
       branch devwork

-m     subcmds/status.py

If the branch is tracking an upstream branch, the number of commits ahead and/or behind is also shown:

project repo/
       branch devwork [ahead 1, behind 2]

-m     subcmds/status.py

The first column explains how the staging area (index) differs from the last commit (HEAD). Its values are always displayed in upper case and have the following meanings:

• -: no difference
• A: added (not in HEAD, in index)
• M: modified (in HEAD, in index, different content)
• D: deleted (in HEAD, not in index)
• R: renamed (not in HEAD, in index, path changed)
• C: copied (not in HEAD, in index, copied from another)
• T: mode changed (in HEAD, in index, same content)
• U: unmerged; conflict resolution required

U is the scary one — conflict resolution required, bestie, go fix it 😭

The second column explains how the working directory differs from the index. Its values are always displayed in lower case and have the following meanings:

• -: new / unknown (not in index, in work tree)
• m: modified (in index, in work tree, modified)
• d: deleted (in index, not in work tree)

---

Repo Manual energy, repo status, June 2026 — that's a wrap, bestie, go forth and status your repos 💜✨🫶