From: Ben Knoble <ben.knoble@gmail.com>
Date: Wed, 14 Jan 2026 21:38:33 GMT
Subject: Re: Triangular workflow
Message-ID: <4F632782-4B1C-452A-A64B-CA223D2C16B0@gmail.com>
In-Reply-To: <20260114162427.GA885771@coredump.intra.peff.net>


> Le 14 janv. 2026 à 11:31, Jeff King <peff@peff.net> a écrit :
> 
>>> Yeah, though @{push} is usually not explicitly configured in the same
>>> way @{upstream} is, but rather a consequence of how push.default and
>>> remote.pushdefault interact. But it was added for exactly this kind of
>>> triangular workflow. I sometimes will do stuff like:
>>> git range-diff origin @{push} HEAD
>> I imagine the same thing could be achieved with
>>  origin/$(git rev-parse --abbrev-ref HEAD)
> 
> Sure, but:
> 
> 1. It is a lot shorter to type @{push}. ;)
> 
> 2. Using @{push} works everywhere, even on my non-triangular repos,

Just so I’m clear, this is only with push.default=current, right? I could never make @{push} work otherwise.