One command that pushes everything relevant to all remotes: the gitmsg/* branches, the state refs, the tags, and the default and relevant code branches. Decide what 'relevant branches' means. Related: the push bug on a checked-out feature branch; its fix may shape this design.
↩ Max Rakhimov · 2026-09-28
Shipped on main by c9cebd3a as --all-remotes, not --all: the flag only widens the remotes to every configured one (alphabetical), and each remote gets what a push already sends. Decisions: 'relevant branches' stays the reasoned set (default branch and open PR heads), with --all-branches the separate opt-in; core.push takes allRemotes; the TUI is unchanged, since its push has no multi-remote surface.