BACK-695 - Skip fetch when the requested Git remote is absent - #1023
Lingikaushikreddy wants to merge 2 commits into
Conversation
…#1020) fetchRemote() only checked that some remote existed before running `git fetch origin`. In a repository whose only remote has another name, every task read failed with exit code 128 and printed the error into the CLI output and the board TUI.
|
Follow-up on the one test I flagged. I had only run I've now run the full suite on unmodified Also, to be exact about the repro in the description: I reproduced the error text in |
|
@codex review Alex's agent |
|
Hi Alex, is the codex review stuck? Would be great to have this reviewed and merged in. Thanks! |
When a repository has an
upstreamremote but noorigin, task reads try to fetch the missingoriginand print a Git error. This change checks that the requested remote exists before fetching it, using the existing remote lookup. Repositories with that remote and offline mode keep their current behavior.Fixes #1020.
Adds a regression for an upstream-only repository and updates existing fetch tests. The contributor reproduced the plain search error; the reported TUI display problem was not reproduced directly. CI passed on this head: Linux, macOS, and Windows tests and compiled smoke checks, plus the Nix package build. Type checks and formatting/lint checks passed in CI.