p already pushes every resolved remote (the configured list; the picker appears only on ambiguity). Add the --all-remotes equivalent as an explicit choice, a picker entry or a shifted key, resolving through client.AllRemotes so the CLI and the TUI cannot drift. Decided: not the default; the default stays the resolved list, matching --all-remotes being a flag, so a new remote never silently joins a push.
↩ Max Rakhimov · 2026-09-30
Fixed on main by #commit:c75e983b4694: the push confirm gains an a choice that re-targets to every configured remote through client.AllRemotes and re-confirms with each remote listed before anything pushes; the prompt leads with how the list was resolved, the one place the TUI shows the push-remote config. Not the default, per the decision. Four invariants are pinned by headless tests. The review caught a leftover debug probe and dead code, both fixed; its claim that the model is not copied per Update was rejected against the value receiver, and the message round-trip that depends on the copy stays, with the comment citing the receiver.