Triangular workflow

From: Harald Nordgren <haraldnordgren@gmail.com>
Date: Jan 13, 2026, 18:35 UTC
Message-ID: <20260113183557.7991-1-haraldnordgren@gmail.com>
In-Reply-To: <20260113170321.GA265671@coredump.intra.peff.net>

> For my triangular workflow the ahead/behind for the push branch is just
> useless noise. I treat my push destination like a mirror, where I always
> just push up everything at the end of the day.

This seems like a sub-optimal workflow 🤗

May I ask where you normally push (unless you only ever push once at the end) of the day? If it's another branch than your mirror, why not set that as your push destination then, and push to your push destination with the longer

    git push origin my-mirror

It makes more sense to me to reserve the shorter and more convenient 'git push' for something you do many times a day.

Harald

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.