blocks|key|2440174|text|拒绝的原因是标签与远程版本失去了同步。这与树枝的行为是一样的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2440175|通过git+pull+--rebase+<repo_url>+%2Brefs/tags/<TAG>与远程标记同步，同步后需要管理冲突。如果您安装了一个diftool+(例如。git+mergetool+meld使用它来同步远程并保持您的更改。|CODE|2440176|您之所以使用--重新设置标志--是因为您希望将您的工作放在远程的上面，这样就可以避免其他冲突。|2440177|另外，我不明白的是，为什么要删除dev标记并重新创建它？标记用于指定软件版本或里程碑。例如git标签v0.1dev、v0.0.1alpha、v2.3-cr(cr+-候选版本)等等。|2440178|解决这个问题的另一种方法是发出一个git+reflog，然后在远程上按下dev标记。以这样的方式复制提交id和git+reset+--mixed+<commmit_id_from_reflog>，您知道您的标记在您按下它的时候与远程同步，并且不会发生冲突。|2440179|entityMap^0|0|2|0|2|19|2D|I|1O|4|0|6|6|0|G|3|1E|7|1M|B|1Y|7|0|H|A|10|3|1J|16|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@$9|U|A|V|B|H]|$9|W|A|X|B|H]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|I|3|J|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|K|3|L|5|6|7|13|8|@$9|14|A|15|B|H]|$9|16|A|17|B|H]|$9|18|A|19|B|H]|$9|1A|A|1B|B|H]]|D|@]|E|$]]|$1|M|3|N|5|6|7|1C|8|@$9|1D|A|1E|B|H]|$9|1F|A|1G|B|H]|$9|1H|A|1I|B|H]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|1J|8|@]|D|@]|E|$]]]|P|$]]

The reason you are getting rejected is that your tag lost sync with the remote version. This is the same behaviour with branches.

sync with the tag from the remote via <code>git pull --rebase &lt;repo_url&gt; +refs/tags/&lt;TAG&gt;</code> and after you sync, you need to manage conflicts.
If you have a diftool installed (ex. meld) <code>git mergetool meld</code> use it to sync remote and keep your changes.

The reason you're pulling with --rebase flag is that you want to put your work on top of the remote one so you could avoid other conflicts.

Also, what I don't understand is why would you delete the <code>dev</code> tag and re-create it??? Tags are used for specifying software versions or milestones. Example of git tags <code>v0.1dev</code>, <code>v0.0.1alpha</code>, <code>v2.3-cr</code>(cr - candidate release) and so on..

<hr>

Another way you can solve this is issue a <code>git reflog</code> and go to the moment you pushed the <code>dev</code> tag on remote. Copy the commit id and <code>git reset --mixed &lt;commmit_id_from_reflog&gt;</code> this way you know your tag was in sync with the remote at the moment you pushed it and no conflicts will arise.

blocks|key|1362363|text|在Mac+SourceTree中，仅取消选择Push+all+tags复选框：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1362364|​|1362365|📷|atomic|1362366|1362367|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/e5d6015010b7c4d677ef1b1bebcaac59.png|imageAlt^0|M|D|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|K|3|G|5|6|7|12|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S|T|-4]]]]

In Mac SourceTree only deselect the Push all tags checkbox:

<a href="https://i.stack.imgur.com/tz6jM.png"><img src="https://i.stack.imgur.com/tz6jM.png" alt="enter image description here"></a>

blocks|key|2440243|text|在Windows+SourceTree中，取消勾选Push+all+tags+to+remotes。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2440244|​|2440245|📷|atomic|2440246|2440247|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/24700b2aef5f750196f0104a3bba029a.png|imageAlt^0|P|O|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|K|3|G|5|6|7|12|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S|T|-4]]]]

In Windows SourceTree, untick <code>Push all tags to remotes</code>.

<a href="https://i.stack.imgur.com/ohQ8H.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ohQ8H.png" alt="enter image description here"></a>

blocks|key|1362439|text|似乎我在这个问题上迟到了，而且/或它已经被回答了，但是，可以做的是：(在我的例子中，我在本地只有一个标签)。我删除了旧标签，然后用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1362440|git+tag+-d+v1.0
git+tag+-a+v1.0+-m+"My+commit+message"|code-block|syntax|javascript|1362441|然后：|1362442|git+push+--tags+-f|1362443|它将更新远程上的所有标记。|offset|length|style|BOLD|1362444|可能很危险！自担风险使用.|1362445|entityMap^0|0|0|0|0|8|2|0|0|D|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Y|8|@$M|Z|N|10|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|11|8|@$M|12|N|13|O|P]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

It seems that I'm late on this issue and/or it has already been answered, but, what could be done is:
(in my case, I had only one tag locally so.. I deleted the old tag and retagged it with:

<pre><code>git tag -d v1.0
git tag -a v1.0 -m "My commit message"
</code></pre>

Then:

<pre><code>git push --tags -f
</code></pre>

That will update all tags on remote. 

Could be dangerous! Use at own risk.

blocks|key|1362478|text|如果您使用的是SourceTree，那么它是非常简单的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1362479|​|1362480|📷|atomic|1362481|基本上，您只需要删除并重新添加冲突的标记：|1362482|转到选项卡Repository+->+Tag+->+删除标记|ordered-list-item|1362483|选择冲突的标记名|1362484|检查所有遥控器中的删除标记，|1362485|按移除|1362486|创建与正确提交的名称相同的新标记|1362487|在将更改推送到远程时，确保检查，推送所有标记|1362488|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/308bbcb4812a0b16090e0892e004e03a.png|imageAlt^0|7|A|0|0|0|1|0|0|0|5|A|J|3|Q|4|0|0|9|5|0|1|2|0|0|F|7|0^^$0|@$1|2|3|4|5|6|7|18|8|@$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1B|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|1C|8|@]|D|@$9|1D|A|1E|1|1F]]|E|$]]|$1|K|3|L|5|6|7|1G|8|@]|D|@]|E|$]]|$1|M|3|N|5|O|7|1H|8|@$9|1I|A|1J|B|C]|$9|1K|A|1L|B|C]|$9|1M|A|1N|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|O|7|1O|8|@]|D|@]|E|$]]|$1|R|3|S|5|O|7|1P|8|@$9|1Q|A|1R|B|C]]|D|@]|E|$]]|$1|T|3|U|5|O|7|1S|8|@$9|1T|A|1U|B|C]]|D|@]|E|$]]|$1|V|3|W|5|O|7|1V|8|@]|D|@]|E|$]]|$1|X|3|Y|5|O|7|1W|8|@$9|1X|A|1Y|B|C]]|D|@]|E|$]]|$1|Z|3|-4|5|6|7|1Z|8|@]|D|@]|E|$]]]|10|$11|$5|12|13|14|E|$15|16|17|-4]]]]

It's quite simple if you're using SourceTree.

<a href="https://i.stack.imgur.com/YI2AF.png" rel="noreferrer"><img src="https://i.stack.imgur.com/YI2AF.png" alt="enter image description here"></a>
Basically you just need to remove and re-add the conflicting tag:

<ol>
<li>Go to tab Repository -> Tag -> Remove Tag</li>
<li>Select the conflicting tag name</li>
<li>Check Remove tag from all remotes</li>
<li>Press Remove</li>
<li>Create new tag with the same name to the proper commit</li>
<li>Make sure to check Push all tags when pushing your changes to remote</li>
</ol>

blocks|key|2440352|text|这里有一些好的答案。特别是@torek的那个。我想我应该把这件事加进去，给那些急匆匆的人一点解释。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2440353|总之，当您在本地移动一个标记时，它会将标记从一个非空提交值更改为一个不同的值。但是，由于git+(作为默认行为)不允许更改非空远程标记，所以不能推送更改。|2440354|解决方法是删除标记(并勾选删除所有遥控器)。然后创建相同的标签并推送。|2440355|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/19300065/1639345^0|D|9|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

Some good answers here. Especially <a href="https://stackoverflow.com/a/19300065/1639345">the one by @torek</a>. I thought I'd add this work-around with a little explanation for those in a rush. 

To summarize, what happens is that when you move a tag locally, it changes the tag from a non-Null commit value to a different value. However, because git (as a default behavior) doesn't allow changing non-Null remote tags, you can't push the change. 

The work-around is to delete the tag (and tick remove all remotes). Then create the same tag and push.

blocks|key|257928|text|我还在想我是怎么进入这种状态的..。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|257929|我找到了一个简单的解决方案--删除所有本地复制的标签，然后从遥控器中取出这些标记。例如：|257930|git+tag+-d+some-tag
git+pull+--tags|code-block|syntax|javascript|257931|不再有冲突和警告。|257932|您可能需要考虑提前备份本地存储库。|257933|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

While I am still wondering how I got into this state...
I found a simple solution - Delete all the local duplicated tags and then pull those tags from the remote. Such as:
<pre><code>git tag -d some-tag
git pull --tags
</code></pre>
No more conflicts or warnings.
You may want to consider backing up your local repository ahead of time.

I get the following error after I run the steps below:

<pre><code>To git@provider.com:username/repo-name.git
 ! [rejected] dev -&gt; 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.
</code></pre>

<ol>
<li>Created the repository</li>
<li>Cloned the repo on the local machine.</li>
<li>Modified the README file, commited the changes and pushed the commit.</li>
<li>Created tag <code>dev</code>: <code>git tag dev</code></li>
<li>Pushed tags: <code>git push --tags</code></li>
<li>Modified the README file, commited the changes and pushed the commit.</li>
<li>Deleted tag <code>dev</code> , created it again and pushed tags:

<pre><code>git tag -d dev
git tag dev
git push --tags
</code></pre></li>
</ol>

Why is this happening?

I am on Mac. My friends that use Linux (Ubuntu) don't have this problem. I know that I can use <code>git push --tags -f</code> to force the tag update, but this is dangerous (e.g. rewriting a commit made by mistake only in the tag, not in the branch).

“tag already exists in the remote" error after recreating the git tag

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

在运行以下步骤后，将得到以下错误：To git@provider.com:username/repo-name.git ! [rejected]        dev -> dev (already exists)error: failed to push some refs to 'git@provider.com:...

问重新创建git标记后，“标记已存在于远程”错误
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问重新创建git标记后，“标记已存在于远程”错误EN