question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: Command failed: git fetch --tags

See original GitHub issue

The issue happens with tags that change their pointer.

❯ git fetch --tags
From gitlab.com:foo/repo
 ! [rejected]        flux-sync  -> flux-sync  (would clobber existing tag)

❯ git fetch --tags -f
From gitlab.com:foo/repo
 t [tag update]      flux-sync  -> flux-sync

Basically need to add -f, if it’s safe globally, or maybe a config option.

Thanks!

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:1
  • Comments:11 (5 by maintainers)

github_iconTop GitHub Comments

3reactions
demisxcommented, Sep 24, 2019

Just to clarify, I meant addition of this --force flag here: https://github.com/semantic-release/semantic-release/compare/master...beocommedia:force-local-tag-updates.

Not sure if doing so makes sense for everyone. For now, I am just running these on CI before invoking npx semantic-release ... and right before publishing to GitLab. This is not perfect, but minimizes chances of flux repo updates interfering with the semantic-release updates.

git fetch -tp -f --all
git tag -d flux-sync-stg || true
git tag -d flux-sync-prod || true
1reaction
manjupriyajaintmcommented, Sep 5, 2019

Hello community, I just found myself with this problem too, but I just solved it.

Surely when running the “react-native upgrade” command, it gave them the message that it was not necessary to update or with the command “react-native eject” that the command is not recognized.

Now you should use the “react-native upgrade --legacy true” command to back up your android folders or ios as the case may be as this command will replace your files.

Now it’s just telling you not to replace your package.json

Greetings.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to get rid of "would clobber existing tag" - Stack Overflow
VSCode will pull all tags by default, thus you get the error. ... by using the command line and manually entering the git...
Read more >
git-fetch Documentation - Git
Fetch branches and/or tags (collectively, "refs") from one or more other repositories, along with the objects necessary to complete their histories.
Read more >
git fetch failed with exit code 1 - Bobcares
Fetch command usually returns exit code 1 due to syntax errors, ... But now it's not, so git fetch --tags can fail if...
Read more >
Git fetch failed with exit code: 129 - Visual Studio Feedback
I am experiencing the error: Git fetch failed with exit code: 129 in checkout. I have a self-hosted agent with linux redhat. The...
Read more >
git-fetch(1) - Arch manual pages
When git fetch is run without specifying what branches and/or tags to fetch on the command line, e.g. git fetch origin or git...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found