Re: [PATCH v7] doc: add new detached HEAD state guide
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Nov 16, 2026, 22:08 UTC
- Message-ID
- <xmqqik1wjuoo.fsf@gitster.g>
- In-Reply-To
- <pull.2250.v7.git.1794843180501.gitgitgadget@gmail.com>
"Julia Evans via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 16 quoted lines
> 1: 64f50b8248 ! 1: 020aac7cc4 doc: checkout: rewrite detached HEAD state explanation > @@ Metadata > Author: Julia Evans <julia@jvns.ca> > > ## Commit message ## > - doc: checkout: rewrite detached HEAD state explanation > + doc: add new detached HEAD state guide > > - The current explanation has the following issues: > + Add a new guide (`git help detached-head`) to help users who > + accidentally end up in detached HEAD state without understanding why. > + Make it dual-purpose so that it can also be used as the DETACHED HEAD > + section in `git-checkout.adoc`. The result is a shorter guide that > + covers more material than the previous section. > + > + This fixes the following issues with the current DETACHED HEAD section:
This makes it clearer what we are doing with this change.
Show 11 quoted lines
> +it lets you easily check out an old version of your project. For > +example, a data scientist could use this to run an old version of a > +data pipeline or a programmer could use this to figure out when a bug > -+was introduced. By detaching `HEAD`, you don't need to create a > -+temporary branch. > ++was introduced. You can also use this to make experimental commits > ++without being on a branch. By detaching `HEAD`, you don't need to create > ++a temporary branch. > + > +But it's important to know that if you create new commits while in > +detached HEAD state, those commits won't be on a branch. This makes
I've stared at this patch for too long that my eyes are contaminated. It would be great if somebody gave a hopefully final pass with a fresh eye before we declare victory and merge it down to 'next'.
Thanks.