Will assigning at tag to a Github Release also assign it to the Commit

Will assigning at tag (e.g. v1.1.0) to a Github release also assign it to the commit, assuming that the specified commit doesn’t already have a tag? If so, will it be a lightweight or annotated tag?

  • Can I add metadata to git commits? Or can I hide some tags in gitk
  • Using git-svn, how do I dcommit tags?
  • How to install a tagged commit from a local Git repository using Composer?
  • Does git-svn support different revisions for each subdirectory?
  • How to checkout from git
  • Output from 'git ls-remote' shows tags not found in 'git tag -l'
  • Why cant i see my git tag on the bitbucket remote repository?
  • `type commit` in an annotated tag in git
  • One Solution collect form web for “Will assigning at tag to a Github Release also assign it to the Commit”

    Will assigning at tag (e.g. v1.1.0) to a Github release also assign it to the commit

    Yes it will.

    If so, will it be a lightweight or annotated tag?

    A lightweight one.


    You can take a look at this sample release that I’ve created through GitHub UI for the sake of answering this question. This repository wasn’t previously bearing any tag.

    Once locally fetched, one can see that a new tag has been added upstream.

    $ ls .git/refs/tags/
    v0.1
    

    And that this tag directly points to a commit (ie. It’s a lightweight tag, not an annotated one).

    $ cat .git/refs/tags/v0.1
    485750d2def0e01f5653534659d1785be0ff73db
    
    $ git cat-file -t 48575
    commit
    
    Git Baby is a git and github fan, let's start git clone.