From: Harald Nordgren <haraldnordgren@gmail.com>
To: phillip.wood123@gmail.com
Cc: git@vger.kernel.org, gitgitgadget@gmail.com, gitster@pobox.com,
haraldnordgren@gmail.com, phillip.wood@dunelm.org.uk
Subject: Re: [PATCH] revisions: add @{default} shorthand for default branch
Date: Mon, 2 Feb 2026 11:14:45 +0100 [thread overview]
Message-ID: <20260202101445.13790-1-haraldnordgren@gmail.com> (raw)
In-Reply-To: <d92bd08f-abee-49a6-89ad-3be5e0c06ad6@gmail.com>
> I don't really understand what you're trying to achieve and I'm not sure
> if the suggestion above is a good idea but it might help understand what
> it is you're trying to do.
I didn't realize I was so bad at explaining 😅
What I want is a shorthand for switching to the local version of the
default branch of the repo. This but with less voodoo:
git switch $(git rev-parse --abbrev-ref $(git remote | rg '^(origin|upstream)$' | tail -n1) | sed 's@.*/@@')
> you say you don't work directly on the main branch but then later on
> you're then creating a release from it. Is "main" just a mirror of
> "origin/main" or are you merging local work into it as well?
My main is a mirror of upstream/main. I never commit to it, just do
'git pull' to create releases.
Also, I switch to it when I discover a bug on my branch, to try to
understand if the bug is already on main or not. It's the baseline all work
is compared against.
>> 99designs/gqlgen
>> refs/remotes/upstream/master
>>
>> amplitude/experiment-react-native-client
>> refs/remotes/upstream/main
>>
>> Antonboom/testifylint
>> refs/remotes/upstream/master
>>
>> cli/cli
>> refs/remotes/upstream/trunk
I want a shorthand so that when in any of these repos, I'm switching to the
default branch, I simply have to run
git switch @{primary}
and I would end up with
99designs/gqlgen
Switched to branch 'master'
amplitude/experiment-react-native-client
Switched to branch 'main'
Antonboom/testifylint
Switched to branch 'main'
cli/cli
Switched to branch 'trunk'
Harald
next prev parent reply other threads:[~2026-02-02 10:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 15:25 [PATCH] revisions: add @{default} shorthand for default branch Harald Nordgren via GitGitGadget
2026-01-29 20:23 ` Junio C Hamano
2026-01-30 10:59 ` Harald Nordgren
2026-01-30 11:12 ` Harald Nordgren
2026-01-30 16:42 ` Junio C Hamano
2026-01-30 20:58 ` Harald Nordgren
2026-01-30 21:56 ` Junio C Hamano
2026-01-31 0:09 ` Harald Nordgren
2026-01-31 19:16 ` Junio C Hamano
2026-01-31 20:22 ` Harald Nordgren
2026-01-31 20:55 ` Harald Nordgren
2026-02-02 12:32 ` Junio C Hamano
2026-02-02 15:30 ` Harald Nordgren
2026-02-02 9:37 ` Phillip Wood
2026-02-02 10:14 ` Harald Nordgren [this message]
2026-02-02 19:40 ` D. Ben Knoble
2026-02-02 21:19 ` Harald Nordgren
2026-02-02 21:53 ` Kristoffer Haugsbakk
2026-02-02 22:17 ` Ben Knoble
2026-02-02 22:54 ` Harald Nordgren
2026-02-02 21:33 ` Junio C Hamano
2026-02-02 22:16 ` Ben Knoble
2026-02-02 23:03 ` Harald Nordgren
2026-02-02 21:44 ` Junio C Hamano
2026-02-02 22:56 ` Harald Nordgren
2026-02-03 11:18 ` Harald Nordgren
2026-02-03 14:38 ` Phillip Wood
2026-02-02 22:28 ` Junio C Hamano
2026-01-30 13:26 ` [PATCH v2] " Harald Nordgren via GitGitGadget
2026-01-30 16:54 ` Kristoffer Haugsbakk
2026-01-30 20:45 ` [PATCH v3] revisions: add @{primary} shorthand for primary branch Harald Nordgren via GitGitGadget
2026-01-31 0:06 ` [PATCH v4] " Harald Nordgren via GitGitGadget
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260202101445.13790-1-haraldnordgren@gmail.com \
--to=haraldnordgren@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=phillip.wood123@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox