Skip to content

[replace tags] error would clobber existing tag #233

Closed
@talset

Description

@talset
Contributor

By using tag and replacing one with git tag -f raise the following git error

From github.com:talset/crappytest
 ! [rejected]        DEV        -> DEV  (would clobber existing tag)

How to reproduce:

git checkout bla
git tag -f DEV
git push origin DEV --force

git checkout foo
git tag -f DEV
git push origin DEV --force

What is done by the resource ?

git fetch --tags
From github.com:talset/crappytest
 ! [rejected]        DEV        -> DEV  (would clobber existing tag)

How to solve it ?

Add a -f flag

git fetch --tags -f
From github.com:talset/crappytest
 t [tag update]      DEV        -> DEV

I will make a PR for this

Activity

added a commit that references this issue on Jan 4, 2019

fix concourse#233 error would clobber existing tag

e9e37d5
added a commit that references this issue on Jan 4, 2019

fix concourse#233 error would clobber existing tag

d9f6cc2
added a commit that references this issue on Jan 15, 2019

Merge pull request #234 from talset/master

b1db5e5
mlorenzatiglb

mlorenzatiglb commented on Sep 13, 2019

@mlorenzatiglb

If it still happens do a yarn cache clean.

adrianbona

adrianbona commented on Nov 18, 2020

@adrianbona

If it still happens do a yarn cache clean.

Oh my gosh, YES

velidan

velidan commented on Feb 15, 2021

@velidan

Thank you. This solution works

vinnyA3

vinnyA3 commented on Apr 13, 2021

@vinnyA3

cache clean worked for me, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @talset@adrianbona@velidan@vinnyA3@mlorenzatiglb

        Issue actions

          [replace tags] error would clobber existing tag · Issue #233 · concourse/git-resource