git-tag

问题 git branch -avv shows all branches (including remote ones), decorating them with the tracking branch, short-SHA and commit title. Is there a similar command to display all tags together with the commit they point to, optionally including whether it is pushed upstream, and additionally with the message if the tag was annotated? The best I could get so far is: git tag --format '%(color:green)%(refname:short)%09%(color:white)%(objectname:short) %(contents:subject)' But this has several problems:

问题 Long story short I'm writing a script to migrate a very large project from (gasp) Microsoft SourceSafe to Git and I'm trying to retain the authors of the SourceSafe project's labels(which are essentially tags in Git). I know you can modify the author and committer name/date of a Git Commit but can you do the same to a Git Tag? 回答1: TL;DR Re-create the tags with the new desired data. But if anyone else had them before, they may not accept your new ones. Or they may! It's up to them , though.

问题 I have a project which I am working by myself (no team). I have tagged some commits like v0.0.1 , v0.0.9 ... v0.9.1 and so on. Now, I would like to rebase them leaving only those version tagged commits, but I have two problems: When I do git rebase -i v0.0.1 (the first version, more than 2000 commits since then) I dont know how to show the tags inside the 'rebase screen', that is where I define squashs; Even if I was be able to see the tags inside the rebase screen it would be so time

问题 Summary How do I get the name of the current git tag in an Azure Devops Pipeline YAML-file? What Am I Trying to Do? I am setting up a build pipeline in Azure Devops. The pipeline triggers when a new git tag is created. I then want to build docker images and tag them with the git tag's name. My YAML pipeline looks something like this: # Trigger on new tags. trigger: tags: include: - '*' stages: - stage: Build jobs: - job: Build pool: vmImage: 'ubuntu-latest' steps: - script: export VERSION_TAG

问题 I have some history rewriting to do for which I'd like to keep my original tree intact for now. The rewritten tree should however copy the tags previously used as well. Is there any less manual option than e.g. prepending tag names with the branch name? 回答1: No, there is nothing like a per-branch tag in git. All branches and tags are just kinds of refs in Git; a ref is just a name that points to a particular revision in the revision history. For instance, if you have devel and master branches

问题 So I've read Git: How to find out on which branch tag is? and many other posts and I already know how to use: git branch --contains tag However, I still need to know how to list branches that contain a given commit (or tag) in specific repository . Background I've extracted a list of tags from a remote repository archive using: git ls-remote --tags archive Now, for each of the tags extracted, I wish to get the list of containing branches. Using command: git branch --contains tag doesn't help

问题 I have a tag already pushed onto the remote, and when another user creates the same tag and tries to push, push will fail because tag already exists on the remote. But I thought if I do --f force tag push, it should be work. But that is not what I see. I think I have to do this. Create tag Push tag -> If push fails -> Delete tag on remote -> push tag again. Is this correct? Isnt force push tag supposed to take care of this? I am using annotated tags with git -a v1.0 -f -m "message" 回答1: In my

问题 I have successfully made, committed, and pushed changes to a central git repository. I realize now that I want to tag the current version of all files. So I do: git tag -a 0.5 That succeeds. But now I try a git push and I am told there's nothing to commit. How do I push my new tag to the central repository? (Note that git tag shows the tag 0.5, but only locally) 回答1: I think you want git push --tags as that, well, pushes all your tags :) There are some alternatives of course, this being git

问题 I understand how it is possible to tag a blob, or a tree, or even another annotated tag, using a git tag. I understand the architecture and conceptual design that makes this possible. However, I'm having trouble thinking of real life applications of this (or "real workflow" applications). Searching here on Stack Overflow I only found one answer that mentions tagging non-commit objects, with advice not to do so. Under what possible circumstances could it ever be appropriate to tag a non-commit

问题 I have a repository in GitHub and I need to tag it. I tagged in a shell, but on GitHub it is not showing up. Do I have to do anything else? The command I used in the shell is: git tag 2.0 And now when I type git tag it shows: 2.0 So it seems like tags are present, correct? The repository is: https://github.com/keevitaja/myseo-pyrocms. How do I make this tag show up on GitHub? Where are my tags? 回答1: You can create tags for GitHub by either using: the Git command line, or GitHub's web