blocks|key|2508602|text|如果你是理智的，编辑配置文件是足够安全的。如果你想变得更偏执，你可以使用瓷器命令来修改它：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2508603|git+config+branch.master.remote+newserver|code-block|syntax|javascript|2508604|当然，如果您在前面和之后查看配置，您将看到它确实完成了您要做的事情。|2508605|但就你个人而言，我会做的是：|2508606|git+remote+rename+origin+old-origin
git+remote+rename+new-origin+origin|2508607|也就是说，如果新服务器要成为规范的远程服务器，为什么不将其称为原始服务器，就像您最初从它克隆的一样？|2508608|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|U|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

If you're sane about it, editing the config file's safe enough. If you want to be a little more paranoid, you can use the porcelain command to modify it:

<pre><code>git config branch.master.remote newserver
</code></pre>

Of course, if you look at the config before and after, you'll see that it did exactly what you were going to do.

But in your individual case, what I'd do is:

<pre><code>git remote rename origin old-origin
git remote rename new-origin origin
</code></pre>

That is, if the new server is going to be the canonical remote, why not call it origin as if you'd originally cloned from it?

blocks|key|2508627|text|您可以删除当前分支并执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2508628|git+branch+--track+local_branch+remote_branch|code-block|syntax|javascript|2508629|或将远程服务器更改为配置中的当前服务器。|2508630|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

You could either delete your current branch and do:

<pre><code>git branch --track local_branch remote_branch
</code></pre>

Or change change remote server to the current one in the config

blocks|key|2508654|text|使用git+v1.8.0或更高版本：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2508655|git+branch+branch_name+--set-upstream-to+your_new_remote/branch_name|code-block|syntax|javascript|2508656|或者您可以使用-u交换机|CODE|2508657|git+branch+branch_name+-u+your_new_remote/branch_name|2508658|使用git+v1.7.12或更早版本|2508659|git+branch+--set-upstream+branch_name+your_new_remote/branch_name|2508660|entityMap^0|2|A|0|0|7|2|0|0|6|7|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Y|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Z|8|@$9|10|A|11|B|M]]|D|@]|E|$]]|$1|N|3|O|5|H|7|12|8|@]|D|@]|E|$I|J]]|$1|P|3|Q|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|R|3|S|5|H|7|16|8|@]|D|@]|E|$I|J]]|$1|T|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|U|$]]

<h2>Using git v1.8.0 or later:</h2>
<pre class="lang-sh prettyprint-override"><code>git branch branch_name --set-upstream-to your_new_remote/branch_name
</code></pre>
<h2>Or you can use the <code>-u</code> switch</h2>
<pre class="lang-sh prettyprint-override"><code>git branch branch_name -u your_new_remote/branch_name
</code></pre>
<h3>Using git v1.7.12 or earlier</h3>
<pre class="lang-sh prettyprint-override"><code>git branch --set-upstream branch_name your_new_remote/branch_name
</code></pre>

blocks|key|952732|text|对我来说，解决办法是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|952733|git+remote+set-url+origin+https://some_url/some_repo|code-block|syntax|javascript|952734|然后：|952735|git+push|952736|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

For me the fix was:

<pre><code>git remote set-url origin https://some_url/some_repo
</code></pre>

Then:

<pre><code>git push
</code></pre>

blocks|key|2508705|text|对于最新的git+(2.5.5)，命令如下：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2508706|git+branch+--set-upstream-to=origin/branch|code-block|syntax|javascript|2508707|这将更新当前本地分支的远程跟踪分支。|2508708|entityMap^0|5|B|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

With an up to date git (2.5.5) the command is the following : 

<pre><code>git branch --set-upstream-to=origin/branch
</code></pre>

This will update the remote tracked branch for your current local branch

blocks|key|2149701|text|对正在发生的事情有很多控制的另一个选项是手工编辑配置：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2149702|git+config+--edit|code-block|syntax|javascript|2149703|或者速记|2149704|git+config+-e|2149705|然后随意编辑该文件，保存并应用您的修改。|2149706|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Another option to have a lot of control over what's happening is to edit your configurations by hand:

<pre><code>git config --edit
</code></pre>

or the shorthand

<pre><code>git config -e
</code></pre>

Then edit the file at will, save and your modifications will be applied.

blocks|key|952834|text|根据我从最新的git+文档中了解到的情况，简要说明如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|952835|git+branch+-u+upstream-branch+local-branch
git+branch+--set-upstream-to=upstream-branch+local-branch|code-block|syntax|javascript|952836|这种用法似乎与urschrei的回答有点不同，因为他的简要说明是：|952837|git+branch+local-branch+-u+upstream-branch+
git+branch+local-branch+--set-upstream-to=upstream-branch+|952838|我猜他们又换了文件？|952839|entityMap|0|LINK|mutability|MUTABLE|url|https://git-scm.com/docs/git-branch^0|B|2|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|12|8|@]|9|@]|C|$G|H]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|C|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

Based on what I understand from the latest git <a href="https://git-scm.com/docs/git-branch" rel="nofollow noreferrer">documentation</a>, the synopsis is: 

<pre><code>git branch -u upstream-branch local-branch
git branch --set-upstream-to=upstream-branch local-branch
</code></pre>

This usage seems to be a bit different than urschrei's answer, as in his the synopsis is: 

<pre><code>git branch local-branch -u upstream-branch 
git branch local-branch --set-upstream-to=upstream-branch 
</code></pre>

I'm guessing they changed the documentation again?

blocks|key|952841|text|这是最简单的命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|952842|git+push+--set-upstream+<new-origin>+<branch-to-track>|code-block|syntax|javascript|952843|例如，给定命令git+remote+-v生成如下所示：|offset|length|style|CODE|952844|origin++ssh://git@bitbucket.some.corp/~myself/projectr.git+(fetch)
origin++ssh://git@bitbucket.some.corp/~myself/projectr.git+(push)
team++++ssh://git@bitbucket.some.corp/vbs/projectr.git+(fetch)
team++++ssh://git@bitbucket.some.corp/vbs/projectr.git+(push)|952845|改为跟踪团队：|952846|git+push+--set-upstream+team+master|952847|entityMap^0|0|0|7|D|0|0|0|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|@$I|X|J|Y|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

This is the easiest command: 

<pre><code>git push --set-upstream &lt;new-origin&gt; &lt;branch-to-track&gt;
</code></pre>

For example, given the command <code>git remote -v</code> produces something like: 

<pre><code>origin ssh://git@bitbucket.some.corp/~myself/projectr.git (fetch)
origin ssh://git@bitbucket.some.corp/~myself/projectr.git (push)
team ssh://git@bitbucket.some.corp/vbs/projectr.git (fetch)
team ssh://git@bitbucket.some.corp/vbs/projectr.git (push)
</code></pre>

To change to tracking the team instead:

<pre><code>git push --set-upstream team master
</code></pre>

blocks|key|2149815|text|在2.7.4等最新git版本中，|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2149816|要更改跟踪分支的git+checkout+branch_name+#分支名称|CODE|2149817|git+branch+--set-upstream-to=upstream/tracking_branch_name+#上游-远程名称|2149818|entityMap^0|1|5|0|8|O|0|0|1M|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|P|8|@$9|Q|A|R|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|S|8|@$9|T|A|U|B|H]]|D|@]|E|$]]|$1|K|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|L|$]]

In latest git version like 2.7.4,

<code>git checkout branch_name</code> #branch name which you want to change tracking branch

<code>git branch --set-upstream-to=upstream/tracking_branch_name</code> #upstream - remote name

blocks|key|952946|text|我发现@critikaster的帖子很有帮助，只是我不得不用GIT+2.21来执行这些命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|952947|$+git+remote+set-url+origin+https://some_url/some_repo
$+git+push+--set-upstream+origin+master|code-block|syntax|javascript|952948|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/users/2449877/critikaster^0|3|C|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

I've found <a href="https://stackoverflow.com/users/2449877/critikaster">@critikaster</a>'s post helpful, except that I had to perform these commands with GIT 2.21:

<pre><code>$ git remote set-url origin https://some_url/some_repo
$ git push --set-upstream origin master
</code></pre>

blocks|key|2149887|text|最简单的方法是简单地推到新的分支：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2149888|git推送-u原点分支/名称|blockquote|2149889|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|H|8|@]|9|@]|A|$]]|$1|E|3|-4|5|6|7|I|8|@]|9|@]|A|$]]]|F|$]]

the easiest way is to simply push to the new branch:

<blockquote>
 git push -u origin branch/name
</blockquote>

blocks|key|2508937|text|在尝试上述操作和搜索、搜索等之后，我发现在本地分支上的服务器上没有任何更改，团队资源管理器中的Visual没有指示此分支跟踪远程分支。偏僻的分支在那里，所以它应该能工作。最后，我删除了github上的远程分支，并再次推送我的本地分支，该分支的更改没有被跟踪，原因不明。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2508938|通过删除远程分支并重新推送未被跟踪的本地分支，在git集线器上重新创建本地分支。我试图在命令提示符下(使用Windows)来跟踪远程分支，直到我这样做为止。一切都恢复正常。|2508939|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

After trying the above and searching, searching, etc. I realized none of my changes were on the server that were on my local branch and Visual Studio in Team Explorer did not indicate this branch tracked a remote branch. The remote branch was there, so it should have worked. I ended up deleting the remote branch on github and 're' Push my local branch that had my changes that were not being tracked for an unknown reason.
By deleting the remote branch and 're' Push my local branch that was not being tracked, the local branch was re-created on git hub. I tried to this at the command prompt (using Windows) I could not get my local branch to track the remote branch until I did this. Everything is back to normal.

blocks|key|953007|text|根据git文档，最好的方法是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|953008|确保实际来源路径：|ordered-list-item|953009|git远程-v|blockquote|953010|然后用以下方式进行更改：|953011|git远程设置-url原点|953012|其中URL+-存储库是我们从克隆选项获得的相同的URL。|953013|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Q|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|R|8|@]|9|@]|A|$]]|$1|H|3|I|5|D|7|S|8|@]|9|@]|A|$]]|$1|J|3|K|5|G|7|T|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|U|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|O|$]]

Based on the git documentation the best way is:
<ol>
<li>be sure the actual origin path:</li>
</ol>
<blockquote>
git remote -v
</blockquote>
<ol start="3">
<li>Then make the change with:</li>
</ol>
<blockquote>
git remote set-url origin 
</blockquote>
where url-repository is the same URL that we get from the clone option.

blocks|key|2149973|text|我尝试了很多解决方案，但从Bitbucket到Azure+Devops迁移，这个解决方案对我很有用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2149974|创建储存库|ordered-list-item|2149975|git克隆源URL|offset|length|style|BOLD|2149976|git配置--全局配置--未设置credential.helper|2149977|git配置credential.helper存储|2149978|git远程rm原点|2149979|git远程将原始URL添加到新的回购中|2149980|git推送原点--全部
在错误情况下使用
git推送-f原点--全部
在访问或标识出错的情况下
转到分支->选择分支->3点->分支安全性->允许强制推进。|2149981|git推送-标签|2149982|entityMap^0|0|0|5|4|0|0|0|0|8|A|0|C|8|Z|6|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|10|8|@$G|11|H|12|I|J]]|9|@]|A|$]]|$1|K|3|L|5|D|7|13|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|14|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|15|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|16|8|@$G|17|H|18|I|J]]|9|@]|A|$]]|$1|S|3|T|5|D|7|19|8|@$G|1A|H|1B|I|J]|$G|1C|H|1D|I|J]]|9|@]|A|$]]|$1|U|3|V|5|D|7|1E|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|X|$]]

I tried lots of solution but this one worked for me from Bitbucket to Azure Devops Migration:
<ol>
<li>Create Repository</li>
<li>git clone Source URL</li>
<li>git config --global --unset credential.helper</li>
<li>git config credential.helper store</li>
<li>git remote rm origin</li>
<li>git remote add origin URL to NEW repo</li>
<li>git push origin --all 
In case error use 
git push -f origin --all 
In case error in access or identity
 go to branch--&gt;select branch-&gt;3 dots--&gt;branch security --&gt; allow force push</li>
<li>git push --tags</li>
</ol>

The <code>central</code> repository had to be set up on a new server, so I created a new remote on my local repo, and pushed to that.

But now when I do <code>git pull</code>, it claims I am up to date. It's wrong&mdash;it's telling me about the old remote branch, not the new one, which I know for a fact has new commits to fetch.

How do I change my local branch to track a different remote?

I can see this in the git config file but I don't want to mess things up.

<pre><code>[branch "master"]
 remote = oldserver
 merge = refs/heads/master
</code></pre>

How to change the remote a branch is tracking?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

必须在新服务器上设置central存储库，因此我在本地回购系统上创建了一个新的遥控器，并将其推送到该服务器上。但是现在当我做git pull的时候，它声称我是最新的。这是错误的--它告诉我的是旧的远程分支，而不是新的分支，因为我知道这个分支有新的提交。如何更改本地分支以跟踪不同的遥控器？我可以在git配置文件中看到这个...

问如何更改一个分支正在跟踪的遥控器？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何更改一个分支正在跟踪的遥控器？EN