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?

  • Git: bare repo converted to working: undoing this
  • Anyone use both Tortoise Git and Subversion on the same machine?
  • Github file history doesn't show all my commits
  • Using Git to version Microsoft Dynamics NAV?
  • Push on gerrit with windows
  • Git wont pull because of changed files
  • How to list all tags pointing to a specific commit in git
  • Gitolite and non-bare repos?
  • Cannot commit the line `Subproject commit`
  • remove a file from GIT control
  • How can I add a directory of files to a set of commits that have already been pushed?
  • git conflict keep original upstream
  • 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.