Re: `git status` output is very misleading after a merge on a "detached HEAD"

From: Michael J Gruber <git@grubix.eu>
Date: Apr 11, 2017, 14:55 UTC
Message-ID: <88df8638-9b7b-42c4-bb34-4e1a49d4c22d@grubix.eu>
In-Reply-To: <CAMLReHYBVmuu5H015N1ShCD0iLNau9oLOabJhQ7xc=58rXQi+Q@mail.gmail.com>

Enis Bayramoğlu venit, vidit, dixit 11.04.2017 10:57:

Show 11 quoted lines

> I've encountered a very misleading output from `git status`. Here's a
> sequence of events that demonstrates the issue:
> 
> $ git --version
> git version 2.12.0
> 
> $ git checkout origin/master
> 
> $ git status
> HEAD detached from origin/master
> nothing to commit, working directory clean

Hmm. My Git would display "detached at" here as long as you are on the commit that you detached from.

Show 18 quoted lines

> $ git merge --ff f3515b749be861b57fc70c2341c1234eeb0d5b87
> 
> $ git status
> HEAD detached from origin/master
> nothing to commit, working directory clean
> 
> $ git rev-parse origin/master
> e1dc1baaadee0f1aef2d5c45d068306025d11f67
> 
> $ git rev-parse HEAD
> 786cb6dd09897e0950a2bdc971f0665a059efd33
> 
> I think it's extremely misleading that `git status` simply reports
> "HEAD detached from origin/master" while this simply happens to be a
> mildly relevant fact about some past state.
> 
> Thanks and regards
>

Well, what do you suggest as an alternative?

Git tells you that you are in detached state and where you came from (detached from).

Michael