Databases
StackOverflow2013
Postsdbo
POChecking out Git tag leads to "detached HEAD state"
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POChecking out Git tag leads to "detached HEAD state"
    primarykey
    data
    text
    <p>I'm developing a deployment script for my git project and I just started using tags. I've added a new tag called <code>v2.0</code>:</p> <pre><code>git tag -a v2.0 -m "Launching version 2.0" </code></pre> <p>And I've pushed this tag to the remote repository</p> <pre><code>git push --tags </code></pre> <p>When I try to execute the deployment script and check out the <code>v2.0</code> tag I get this message:</p> <blockquote> <p><em>You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b new_branch_name HEAD is now at</em></p> </blockquote> <p>Is that normal? The repository is in limbo because if I do:</p> <pre><code>git branch </code></pre> <p>I get this output:</p> <pre><code>* (no branch) master </code></pre> <p>Sorry if this is obvious but I couldn't figure it out.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USKhriz
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POChecking out Git tag leads to "detached HEAD state"
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POChecking out Git tag leads to "detached HEAD state"
      1. USDi Wu
      1. VTFavorite
    3. VO
      singulars
      1. POChecking out Git tag leads to "detached HEAD state"
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhen you say, "execute the deployment script and checking out the v2.0" does your code look like, "git checkout v2.0"? I'm trying to revamp my release script and when I run "git checkout v2.0" from my production machine I get, "error: pathspec 'v2.0' did not match any file(s) known to git." Even though I've run, "git push origin --tags" on my local machine before doing the "git checkout v2.0" on production. I've also tried running, "git pull --tags" and "git fetch --tags" on production prior to calling "git checkout v2.0" and that doesn't work either... I'm still getting the error. Any Ideas?
      singulars
      1. POChecking out Git tag leads to "detached HEAD state"
      1. USJohn Erck
    2. COI was about to delete the above comment but then figured keeping it up might help somebody else. I was getting the error because I had a TYPO in my tag name when I was running, "git checkout v2.0". However, the typo related error is the exact same error you'll get if you run, "git checkout v2.0" WITHOUT a typo BEFORE running, "git fetch --tags". So, ultimately, my problem was solved by running, "git fetch --tags" PRIOR to running, "git checkout v2.0" without any typos. Phew!
      singulars
      1. POChecking out Git tag leads to "detached HEAD state"
      1. USJohn Erck
    3. CONice, yeah you need to do fetch --tags before (or git fetch that will pull all from remote) so git can checkout the tag. Sorry I just saw your comment today.
      singulars
      1. POChecking out Git tag leads to "detached HEAD state"
      1. USKhriz
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload