gitwig

📂 Item status indicators

Each repository card shows icons and badges reflecting its state:

General Icons

• 📌 (or [P]) — Pinned repository.
• ★ (or *) — Starred / favorite repository.
• ● clean (or * clean) — Clean Git repository (in sync, no changes).
• ○ dir (or o dir) — Directory exists but is not a git repository.
• ✕ missing (or x missing) — Path does not exist or is not a directory.
• [x] / [ ] — Multi-select checkbox, shown on every card once at least one repository is selected with Space.

Compact Status Suffixes

For git repositories, the status indicator shows compact counts for any non-zero values:

Suffix	Meaning	Colour
N+	N files staged for commit	Cyan
N!	N files modified but not staged	Yellow
N?	N untracked files	Muted
N✕	N conflicted files	Red / Danger
N↑	N commits ahead of upstream (needs push)	Bold Green
N↓	N commits behind upstream (needs pull/fetch)	Bold Yellow

When all counts are zero, the indicator shows ● clean. Press ? or h at any time to see the legend inside the app.

⚠ Staging Divergence (⚠ PARTIAL)

When a repository has both staged changes and unstaged changes (modified or untracked) coexisting simultaneously, Gitwig will display a yellow ⚠ PARTIAL warning badge next to the repository name on its card.

Active Repository State Badges

When a repository has an active Git operation or special state, Gitwig displays a colored status badge:

• ✓ CLEAN — No active Git state/operation.
• ⚠ MERGE_HEAD — Active Merge session (contains conflicts).
• 🚧 REBASING — Active Interactive/Normal Rebase.
• ⚡ CHERRY-PICK — Active Cherry-pick operation.
• ⚡ REVERTING — Active Revert operation.
• 🔍 BISECTING — Active Bisect session.
• 📬 APPLYING — Applying patches (mailbox).

Git LFS Badges ([LFS])

Files tracked by Git LFS will display a blue [LFS] badge next to their names in:

• Staged / Unstaged / Conflicts file panels (Workspace tab).
• Changed files lists (Commit Details / Inspect window).
• Repository Files Tree list (Files tab).
• Stashed Files list (Stashes tab).

Global Summary Header Bar

The high-level dashboard stats at the top of the homepage show:

• repos: Total number of configured repositories. If stale projects are hidden via configuration (show_stale_projects), the dashboard shows <visible>/<total> repositories, indicating how many are hidden due to being stale.
• dirty: Repositories with uncommitted/unstaged changes.
• ahead: Repositories with local commits ahead of their remote tracking branch.
• stale: Repositories where the last commit is older than the configured threshold (default is 1 month; configurable via stale_threshold_months in settings).

The four sections render as tabs and double as filters: click one, or cycle with Tab / Shift+Tab, to show only the matching repositories. The active tab is drawn as a highlighted block, and Esc returns to the unfiltered list. When a sticky label filter is active (L), the applied label is pinned as a ● label ▶ chip at the left of the tab strip — click it to reopen the label picker — and all tab counts scope to that label.

Auto-Refresh & Manual Refresh

Items support ~ and ~/... expansion, so ~/code/gitwig resolves to your home directory.

Gitwig automatically refreshes all repository statuses in the background every 10 seconds using non-blocking background threads, ensuring the home dashboard is always live and up-to-date. You can also press R to manually refresh the selected item’s status immediately (e.g. after running a git command externally); the status bar briefly flashes Refreshed to confirm.

Fetch Outcome Indicators

Besides the manual bulk fetch (F), Gitwig also fetches repositories automatically in the background on a schedule: every auto_fetch_interval_mins minutes (default 10, 0 disables), with an optional per-repository interval override in the Repository Settings popup (s on the Overview screen).

While a fetch round is running, each card’s status column shows a Braille spinner and fetching.... When the fetch finishes, the outcome replaces the status for about 30 seconds:

Indicator	Meaning
✓ done	The remote was reached and refs were updated.
✗ auth denied	Credentials were rejected, or the account lacks permission on this remote.
✗ host key	The remote’s SSH host key is unknown, changed, or could not be verified.
✗ not found	The remote URL resolves, but the repository does not exist or is not visible.
✗ unreachable	DNS, routing, TLS, or proxy failure — the host could not be contacted.
✗ no remote	The repository has no remote configured, so there is nothing to fetch. Shown in warning colour rather than error colour.
✗ timed out	The remote accepted the connection but did not reply within fetch_timeout_secs.
✗ local error	Git refused the fetch locally (lock file, unwritable ref, and similar).
✗ failed	The failure did not match a known category; open the details for the raw output.

Successful results fade after the 30-second window and the card returns to its normal status. Failures are kept so an unreachable repository does not silently look healthy again — after the window the card shows its normal status with a small trailing ✗.

Press E on a failed repository to open the full, sanitised git output along with the remote URL and a suggested remedy. Gitwig never lets git, ssh, or a credential helper prompt on the terminal, so a private or unreachable remote can no longer corrupt the display or hang the app.

This site is open source. Improve this page.