1REPO(1)                           Repo Manual                          REPO(1)
2
3
4

NAME

6       repo - repo status - manual page for repo status
7

SYNOPSIS

9       repo status [<project>...]
10

DESCRIPTION

12       Summary
13
14       Show the working tree status
15

OPTIONS

17       -h, --help
18              show this help message and exit
19
20       -j JOBS, --jobs=JOBS
21              number  of  jobs to run in parallel (default: based on number of
22              CPU cores)
23
24       -o, --orphans
25              include objects in working directory outside of repo projects
26
27   Logging options:
28       -v, --verbose
29              show all output
30
31       -q, --quiet
32              only show errors
33
34   Multi-manifest options:
35       --outer-manifest
36              operate starting at the outermost manifest
37
38       --no-outer-manifest
39              do not operate on outer manifests
40
41       --this-manifest-only
42              only operate on this (sub)manifest
43
44       --no-this-manifest-only, --all-manifests
45              operate on this manifest and its submanifests
46
47       Run `repo help status` to view the detailed manual.
48

DETAILS

50       'repo status' compares the working tree to the staging  area  (aka  in‐
51       dex), and the most recent commit on this branch (HEAD), in each project
52       specified. A summary is displayed, one line per file where there  is  a
53       difference between these three states.
54
55       The -j/--jobs option can be used to run multiple status queries in par‐
56       allel.
57
58       The -o/--orphans option can be used to show objects  that  are  in  the
59       working  directory,  but  not  associated with a repo project. This in‐
60       cludes unmanaged top-level files and  directories,  but  also  includes
61       deeper items. For example, if dir/subdir/proj1 and dir/subdir/proj2 are
62       repo projects, dir/subdir/proj3 will be shown if it  is  not  known  to
63       repo.
64
65       Status Display
66
67       The  status display is organized into three columns of information, for
68       example if the file 'subcmds/status.py'  is  modified  in  the  project
69       'repo' on branch 'devwork':
70
71       project repo/
72              branch devwork
73
74       -m     subcmds/status.py
75
76       The first column explains how the staging area (index) differs from the
77       last commit (HEAD). Its values are always displayed in upper  case  and
78       have the following meanings:
79
80       -:     no difference
81
82       A:     added         (not in HEAD,     in index                     )
83
84       M:     modified      (    in HEAD,     in index, different content  )
85
86       D:     deleted       (    in HEAD, not in index                     )
87
88       R:     renamed       (not in HEAD,     in index, path changed       )
89
90       C:     copied        (not in HEAD,     in index, copied from another)
91
92       T:     mode changed  (    in HEAD,     in index, same content       )
93
94       U:     unmerged; conflict resolution required
95
96       The  second  column explains how the working directory differs from the
97       index. Its values are always displayed in lower case and have the  fol‐
98       lowing meanings:
99
100       -:     new / unknown (not in index,     in work tree                )
101
102       m:     modified      (    in index,     in work tree, modified      )
103
104       d:     deleted       (    in index, not in work tree                )
105
106
107
108repo status                        July 2022                           REPO(1)