git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Possible bug report: git checkout tag problem

From
MFMyles Fong <i@myles.hk>
Date
Jan 8, 2018, 03:50 UTC
Message-ID
<160d3e3f291.df909f06277296.7997490218741761365@myles.hk>
Hi,

Brief description: When two tags are pointing to the same commit, e.g. tagA and tagB, if I do `git checkout tagA` then `git checkout tagB`, and then `git status`, it shows `HEAD detached at tagA`

Expected behaviour: I'm expecting it to show `HEAD detached at tagB`, though I understand this makes no difference for the repo code, but still a bit confusing for me.

Found workaround: If I do an extra step `git checkout master`, followed by `git checkout tagB`, and then `git status`, it shows `HEAD detached at tagB` as expected. ("master" can be any branch name)

Affected version: This happens with the latest git version 2.14.3.

Detailed background: We have a system consists of many git repos, and are using tags of global version numbers to ensure the same version of repos are deployed in the whole system. Sometimes when we have a new minor version of the system, there is no new commits for some repos. Still we need a new version tag for those repos to match the system version number, so we put a new version tag pointing to the same commit as the previous version tag. This is how we ran into the above situation and I was suspecting that our deploying script didn't run properly when I see `HEAD detached at {old-version}` in some locations of a {new-version} system. I'm not sure if this is an expected behaviour or not because I didn't found any useful information after some Goolgling, except the following discussion.

Related discussion: I found this discussion to be related to the same problem: https://stackoverflow.com/questions/30631000/git-checkout-tag-issues-tag-is-unchanged/30631434#30631434

Regards, Myles Fong

Next: Johannes Schindelin
Message 1 of 2 in “Possible bug report: git checkout tag problem”
  1. Myles FongJan 8, 2018
  2. Johannes SchindelinJan 8, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.