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: Pushing Single Commits, Reordering with rebase, Duplicate Commits
  • git push fails unless I do a gc on the remote repo first
  • how to show differences betwen some or all files? GIT
  • Fetching all tags from a remote with git pull
  • How do I ignore file deletions in a git branch for merging purposes?
  • Want git post receive hook to make new commit and push
  • How do you tell git to permanently ignore changes in a file?
  • List of remotes for a git repository?
  • How can I determine whether a git submodule is actually ahead or behind its remote?
  • How to synchronize a GIT repository with SVN?
  • Remove all deleted files from “changed but not updated” in Git
  • Git rebasing not working correctly?
  • 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.