From dc57529f0f45c1b2af07509e59bb13b9c708283a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20M=C3=BCller?= Date: Thu, 17 Sep 2026 13:23:34 +0000 Subject: [PATCH] :memo: Correct the upstream claim in branch.sh `main` tracks `origin` (ssh); the comment claiming it tracked an https companion remote was stale. --- scripts/branch.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/scripts/branch.sh b/scripts/branch.sh index 4c7cd19..044df9b 100755 --- a/scripts/branch.sh +++ b/scripts/branch.sh @@ -73,9 +73,9 @@ git show-ref --verify --quiet "refs/heads/${BASE}" || { exit 1 } -# Derive the remote rather than hardcoding it: this repo has `origin` (ssh) and -# `origin_https`, and `main` tracks the latter — `git fetch origin main` would -# check currency against a ref that is never updated here. +# Derive the remote rather than hardcoding it: `main` tracks `origin` (ssh) +# here; a hardcoded name would check currency against a ref that may not +# exist on a differently configured clone. # `--quiet` echoes the unresolved `main@{upstream}` literal to stdout on # failure, so it cannot be paired with a `$(...) || fallback`; the non-quiet # form prints nothing on failure and the fallback runs.