git-tag

Is there a way to keep my local git tags in lockstep with a remote's tags? That is -- not only get new tags when created (as usual, when fetch -ing/ pull -ing), but also prune tags no longer on a remote and also delete existing tags when someone else git push -f 's a tag. I know I can git fetch remotename followed by git remote prune remotename to achieve similar behaviour for branches. ...also prune tags no longer on a remote git fetch gets with Git 2.17 (Q2 2018) an handy short-hand for getting rid of stale tags that are locally held. See commit 6317972 , commit 97716d2 , commit e249ce0 ,

I get the following error after I run the steps below: To git@provider.com:username/repo-name.git ! [rejected] dev -> dev (already exists) error: failed to push some refs to 'git@provider.com:username/repo-name.git' hint: Updates were rejected because the tag already exists in the remote. Created the repository Cloned the repo on the local machine. Modified the README file, commited the changes and pushed the commit. Created tag dev : git tag dev Pushed tags: git push --tags Modified the README file, commited the changes and pushed the commit. Deleted tag dev , created it again and pushed tags

I'm developing a deployment script for my git project and I just started using tags. I've added a new tag called v2.0 : git tag -a v2.0 -m "Launching version 2.0" And I've pushed this tag to the remote repository git push --tags When I try to execute the deployment script and check out the v2.0 tag I get this message: 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,

I've seen a lot of projects using v1.2.3 as the naming convention for tags in git. I've also seen some use 1.2.3 . Is there an officially endorsed style, or are there any good arguments for using either? peritus Version 1.0.0 of Semantic Versioning , by Tom Preston-Werner of GitHub fame, had a sub-specification addressing this: Tagging Specification (SemVerTag) This sub-specification SHOULD be used if you use a version control system (Git, Mercurial, SVN, etc) to store your code. Using this system allows automated tools to inspect your package and determine SemVer compliance and released

Since I created my repository it appears that the tags I have been creating are not pushed to the repository. When I do git tag on the local directory all the tags are present, but when I logon to the remote repository and do a git tag , only the first few show up. What could the problem be?. eevar You could do this: git push --tags In default git remote configuration you have to push tags explicitly (while they are fetched automatically together with commits they point to). You need to use $ git push <remote> tag <tagname> to push a single tag, or $ git push <remote> --tags to push all tags

Say I've forked a node module with a bugfix and I want to use my fixed version, on a feature branch of course, until the bugfix is merged and released. How would I reference my fixed version in the dependencies of my package.json ? hurrymaplelad From the npm docs : git://github.com/<user>/<project>.git#<branch> git://github.com/<user>/<project>.git#feature\/<branch> As of NPM version 1.1.65, you can do this: <user>/<project>#<branch> per @dantheta's comment: As of npm 1.1.65, Github URL can be more concise user/project. npmjs.org/doc/files/package.json.html You can attach the branch like user