Skip to content

Git

Repositories

One list of the repositories behind your running servers, agents and Storage folders — where each branch stands, what has sat still, and a way into each.


Opening the list#

Under the summary at the top of Servers sits a one-line card, Repositories, with a count — 3 found, or “None found yet” — and an arrow button, Open repositories. When no server is running, the card sits under the empty list instead. It stays hidden while there is nothing behind it: with no repository listed and no Storage scan ever run, the list could only say it is empty.

Wherever the card shows, you can also press R on the servers list, or open Quick actions with Q and type repos. The list replaces the servers list, the way a server's screen does. Back to servers, ← or Esc takes you back.

What is listed#

The line under the title says where the list comes from: “From your running servers, agents and Storage folders.” It is not every checkout on your disk — only these:

  • The repository each running server was started from, whether it runs on this computer, in WSL or in a container.
  • The repository each agent session on this computer is working in.
  • Each Storage folder that is itself the top of a repository.
  • The repositories the last Storage scan found, while they still sit under one of your Storage folders or a running server's repository. Remove a folder from Storage and what the scan found there leaves with it. The scan is the one Storage runs when you ask it to.

Each working tree is one row, however many of these name it, and a linked worktree is a row of its own rather than part of the main checkout's. Servers and agents are worked out afresh on every read, and a stopped server's repository leaves the list unless Storage knows it too. Only the last Storage scan's finds are remembered between runs, so they are back straight after a restart without a new scan. A folder whose .git has gone since then simply drops out.

What the screen says#

Storage line
Storage scanned 2 hours ago, or “Storage not scanned yet”, always under the title — how old the scan's part of the list is. Run a Storage scan to bring it up to date.
Scan limit
“The last Storage scan stopped at a limit, so some repositories under your Storage folders may be missing.” What the scan found before it stopped is still listed.
No git
“git isn't on PATH, so Pip can't check working trees with it.” Shown when git did not answer git --version and at least one row is on this computer. The list is read without git, so only Check with git goes missing.
Reading
Placeholder rows while the list is read for the first time.
Nothing yet
“No repositories found yet”, with a line saying that repositories behind running servers and agents show here, and so do the ones a Storage scan finds.
Could not read
“Pip couldn't read the repositories.” with Try again. The last list stays on screen underneath.

Reading a row#

Each row is a card titled with the folder's name, with its full path underneath. The badges below say what HEAD is and where the repository lives:

Branch
The branch checked out. A long name is cut short; hover it for the whole name.
Detached
The short commit and detached — mid-rebase, or checked out to a tag or a specific commit.
No commits yet
A branch with nothing on it yet, such as a new repository before its first commit.
HEAD unreadable
Pip could not read what HEAD points at.
Refs Pip can't read
The repository keeps its refs in git's reftable format, which Pip does not read, so the row has no branch, no upstream and no idle-branch count. More on unusual repositories.
Worktree or submodule
Linked worktree for a checkout made with git worktree add, Submodule for a repository inside another.
WSL or Container
Where the repository lives when it is not on this computer — see below.
Running
Running: 2 servers, 1 agent, with a dot, while anything runs from it.
Storage
Otherwise, how the list found it: Storage folder or Found by Storage scan.

The lines under each row#

HEAD moved
HEAD moved 3 hours ago, from the newest entry in the working tree's own HEAD reflog — a commit, a checkout, a reset. “No history of moves” means git keeps no reflog for HEAD here; “When HEAD last moved is unknown” means Pip could not read it.
git last wrote here
When git last wrote HEAD, the branch or the index, shown only when that came well after HEAD last moved. Staging a change counts; editing a file, on its own, does not.
Upstream
Where the branch stands against the branch it tracks, and when the repository last fetched, in the Git tab's words: “In sync · Fetched 2 hours ago”, “2 ahead, 5 behind · Never fetched”, “Not tracking a remote branch · Never fetched”. “Upstream branch deleted” is drawn as a warning. It is only as fresh as the last fetch, made by Pip or by anything else — more on fetching and sync.
Idle branches
7 of 12 branches not moved in 30 days counts the local branches whose own reflog has not moved for longer than your stale setting. When there are any, it adds 3 whose history git pruned (the reflog was emptied, by git gc or git reflog expire) and 2 with no history (no reflog at all). Neither has a date, so neither counts as idle. At least means the listing stopped short of every branch, and “Pip couldn't read every branch” that it stopped before finding any.
Stale setting
The number of days comes from Settings → Git → Call a branch stale after: 14, 30 (the default), 60 or 90. It is the same setting that marks branches stale in the Branches review. Change it and the list uses the new value from its next read.
LFS objects
For a repository with a Git LFS store, how much it holds: LFS objects: 1.2 GB, at least a size when the count stopped short, or that Pip could not read the folder.

WSL and container rows

A repository behind a server in WSL or a container is listed from what the scan saw, and nothing about it is read from here. The row says “In WSL: listed from what the scan saw, not read from here.” or “In a container: listed from what the scan saw, not read from here.” Its branch and upstream come from the scan; there is no HEAD, idle-branch or LFS line, and no Open folder or Check with git. Agent sessions and Storage folders inside WSL add no row. If a container's folder also arrives another way — as a Storage folder, say — it becomes an ordinary row and is read like one.

Open, copy, check#

Open folder
Opens the working tree in your file manager. Rows on this computer only.
Open on the web
Opens origin's page in your browser — git@github.com:me/app.git opens https://github.com/me/app. Offered only when origin's URL names a host and a path, so a remote that is a local folder or a file:// URL has none. It works for WSL and container rows too.
Copy path
Puts the path, as the row shows it, on the clipboard — “Path copied”. Every row has it.
Check with git
Runs git status once and shows git's answer: “No changes”, or counts such as “4 changed · 2 staged · 3 new files”, with git checked just now beneath. A new folder counts as one new file, as git status lists it. When git needs longer than 10 seconds, the row says “Too big for git to check in 10 seconds.” When git fails, the row quotes its reason. Offered only on rows on this computer, and only when git answers.

When a row has changed under you, the action says so instead of guessing. A deleted folder gets “This folder is gone.” A folder that is no longer a repository gets “This folder is no longer a repository's working tree.” And when the list on screen is older than the one Pip holds, it reads the list again and says “The list changed, so Pip read it again. Try once more.”

What runs, and what goes online

The list is read straight from the files in each .git folder, and reading it writes nothing. Pip runs the git on your computer only for Check with git, and for git --version to know whether to offer it — and it runs the check so that git does not rewrite the index either. Nothing on this list reaches the network itself: Open on the web hands an address to your browser. There is no fetch here; that lives on a server's Git tab.

Finding a repository#

Press / and type. The search matches folder names, branches (or the short commit of a detached HEAD), paths, origin's URL and the upstream, such as origin/main, whatever the case. In the search box, Esc clears what you typed before a second press closes the list. With no match, it says so: No repositories match “acme”.

Rows with something running come first, then the rest by when HEAD last moved, newest first. Rows Pip could not date come after every dated one, and ties go by name and path, so the order holds still between reads. The list draws 100 rows at a time; Show 100 more, or however many are left, draws the next.

The list reads itself again when a Storage scan finishes, when a Storage folder is added or removed, when the servers or agents behind it change, and when you come back to the window more than 30 seconds after the last read. It never reads on a timer or while the window is hidden. Read again, the refresh button beside the title, reads it now.

Did this page not answer it? Tell us what you were looking for — that is how Pip's documentation gets written.