Git
Git notifications
Three notifications about the repositories behind servers on this computer — what sets each one off, and how to mute a repository or switch a kind off.
An operation left unfinished#
When a merge, rebase, cherry-pick, revert or git am session stops part-way in the working tree a server is running from, and nothing moves for ten minutes, a notification titled with the server's name says “A rebase has been in progress for 20m while :5173 is serving”. Under it is “Finish or abort it; the server is serving a half-applied tree” for a rebase or a merge, or “Finish or abort it” for the others.
The ten minutes count from git's last step in the operation, or from when the server started if that is later; the time in the sentence is how long the operation has been under way. Each stall is told once. A step such as git rebase --continue starts the clock again, and if the operation stops again, you hear about it again. A bisect never notifies — sitting on one commit after another is what a bisect is for. How the Git tab shows an operation in progress.
An upstream deleted#
“origin/feature/x was deleted”, with “Its remote-tracking branch is no longer in this repository” under it. It comes when the remote-tracking branch your checked-out branch tracks was there at Pip's last look and is gone at this one. That is usually a fetch with pruning — git fetch --prune, git remote prune origin, or an editor set to prune — removing a branch someone deleted on the remote, often once it was merged.
Pip's own fetch never prunes, so it never sets this off. And Pip says only what it watched happen: an upstream already missing the first time it looked, one missing on a branch you switch to, an upstream that is a local branch, or a ref it could not read never notifies. Each disappearance is told once. From then on, the server's row in the tray menu says upstream gone as well.
Falling further behind#
“main is 3 commits behind origin/main”, with “origin/main moved just now · :5173 is serving” under it. It comes when the branch's remote-tracking branch moves — after any fetch: Pip's, the 15-minute schedule's, your terminal's or your editor's — and a count taken from its new position within two minutes puts the branch further behind than the count before it. There is one per repository every ten minutes at most, so an editor that fetches every few minutes does not become a notification every few minutes.
Why it may never come
The count comes from git's commit-graph, which has to hold both your branch's commit and the one origin just moved to. git writes that file during gc and maintenance, not after every fetch, so in many repositories this notification simply never arrives. It also needs a count from before the move — a branch the row showed in sync or with arrows has one, a branch showing not synced does not — and it never comes for a shallow clone. To make it dependable, have git write the graph on every fetch by setting fetch.writeCommitGraph to true. More on when there is no count.
Clicking a notification#
Click a notification and Pip opens on that server's Git tab. If the server has stopped by then, you get “The server that notice was about has stopped.” instead.
Each notification carries one button, Mute this repository. It mutes the repository the notification was about without opening Pip, covers every worktree of that repository, and still works after the server has stopped.
Muting from the Git tab#
At the foot of the Git tab's Repository card, a line says where the repository stands, with a button to change it:
- Notifications on
- “Git notifications on” — at least one kind is switched on, and this repository is not muted. Mute silences this repository.
- Muted
- “Git notifications muted for this repository”. Unmute lets them through again.
- Off in Settings
- “Git notifications are off in Settings” — all three switches are off. Mute still works, and holds when you switch them back on.
A mute belongs to the repository, not to a server or a worktree, so every worktree of it shares one. WSL and container rows have no such line, because Pip never notifies about them. If the change cannot be saved, Pip says “Couldn't change the mute.”
Switches and the muted list#
Settings → Git — press , for Settings — has a Git notifications group with a switch for each kind, all on by default:
- Notify when a merge, rebase or other git operation sits unfinished for 10 minutes
- Notify when a branch's upstream is deleted
- Notify when a branch falls further behind after a fetch
Below them, Muted repositories lists each muted repository by folder, with Unmute beside it. Muting happens from a notification or the Git tab; Settings only unmutes. Up to 32 repositories stay muted, and muting a 33rd lets go of the oldest mute. At the defaults, the Git row on the Settings index reads “Stale after 30 days”; switched-off notifications, mutes and auto-fetch go in front of it — for example, “2 of 3 notifications on · 1 muted · Stale after 30 days”.
What all three have in common#
- Servers on this computer only. Pip watches the repositories behind servers running directly on this computer — not in WSL, not in a container, not served from a
\\wsl.localhostshare — once per working tree, however many servers run from it. A notification takes the name of the server there with the lowest port, and a click opens that one. - Read, never changed. Every 10 seconds, Pip reads a few files in
.git:HEAD, the branch's tracking settings, the remote-tracking branch, the commit-graph and git's markers for an operation in progress. It runs no git, writes nothing and uses no network, and it keeps watching whether or not its window is open. - Three a minute at most. Across every repository. Any more in that minute are dropped, not saved for later — a tool pruning ten clones at once is one burst, not ten notifications.
- Shown while you are looking. Agent notifications stay quiet while you are looking at the Agents tab; these appear even while that server's Git tab is open in front of you, because nothing in the window announces a stall or a deleted branch as it happens.
- No catching up. Something that happened while its switch was off or its repository muted is not told later, when you turn it back on.
Did this page not answer it? Tell us what you were looking for — that is how Pip's documentation gets written.