Archived
Fetch in the background and follow changes in the repositories
- On startup, after the local state is shown, fetch the superproject and every initialized submodule (all remotes, prune, at most 8 at once). Fetches never prompt; failures show git's message. --no-fetch skips it, f fetches again. - The header shows "fetching n/m", then the fetch age and failures; the detail pane shows each submodule's last fetch and fetch errors. - The git provider polls each repository's metadata (refs, HEAD, index, .gitmodules) every 2 s and reports changes. The app reloads only what changed, keeping old values, expansion and cursor; loads are single-flight with coalesced reruns. Refresh is driven by the repositories, so a fetch in another shell updates the view like ours. - r reloads everything (worktree edits are not watched). - Docs: F50-F53, N1/N8 rewritten, D18-D20 (D12 superseded). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
19c6f17eb2
commit
27f0c0b5d2
@@ -12,3 +12,17 @@ type statusLoadedMsg struct {
|
||||
status *submodule.Status
|
||||
err error
|
||||
}
|
||||
|
||||
// fetchDoneMsg reports one finished fetch. It only updates the fetch
|
||||
// progress; refreshing is left to the watcher, which also sees fetches made
|
||||
// outside the application.
|
||||
type fetchDoneMsg struct {
|
||||
path string // "" is the superproject
|
||||
err error
|
||||
}
|
||||
|
||||
// changeMsg is a change reported by the provider's watcher.
|
||||
type changeMsg struct {
|
||||
change submodule.Change
|
||||
closed bool // the watcher stopped
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user