blocks|key|726244|text|如果您还没有推送到原点，可以通过以下方式将您的分支重置为upstream分支：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|726245|git+checkout+mybranch
git+reset+--hard+origin/mybranch|code-block|syntax|javascript|726246|(确保您在一个单独的分支中引用了您的最新提交，就像您在问题中提到的那样)|726247|请注意，就在重置之后，mybranch@{1}引用了重置之前的旧提交。|style|CODE|726248|但是，如果您已经推送，请参阅"Create+git+branch,+and+revert+original+to+upstream+state“以了解其他选项。|726249|726250|对于Git2.23(2019年8月)，这将是一个命令：。|BOLD|726251|即：git+switch+-C+mybranch+origin/mybranch|726252|示例|726253|C:\Users\vonc\git\git>git+switch+-C+master+origin/master
Reset+branch+'master'
Branch+'master'+set+up+to+track+remote+branch+'master'+from+'origin'.
Your+branch+is+up+to+date+with+'origin/master'.|726254|这会恢复索引和工作树，就像git+reset+--hard一样。|726255|726256|正如Brad+Herman所评论的，reset+--hard将移除任何新文件或将修改后的文件重置为HEAD。|726257|实际上，为了确保您从头开始，重置后的git+clean+-f+-d将确保工作树与您刚刚重置到的分支完全相同。|726258|726259|此blog+post建议使用这些别名(仅适用于master分支，但您可以调整/扩展这些别名)：|726260|726261|别名reset原点=+!git获取原点&&+git+reset+--硬原点/主设备&&+git+clean+-f+-d+reset上游=+!git+fetch上游&&+git+reset--硬上游/master+&&+git+clean+-f+-d|blockquote|726262|726263|然后，您可以键入：|726264|git重置上游|726265|或|726266|git重置原点|726267|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/2739376/definition-of-downstream-and-upstream/2749166#2749166|1|https://stackoverflow.com/a/773728/6309|2|https://git-scm.com/docs/git-switch#Documentation/git-switch.txt--Cltnew-branchgt|3|https://stackoverflow.com/users/259628/brad-herman|4|http://ocpsoft.org/tutorials/git/reset-and-sync-local-respository-with-remote-branch/^0|S|8|0|0|0|0|B|C|0|F|1K|1|0|0|2|G|0|2|12|2|12|2|0|0|0|D|G|0|0|I|C|V|M|2|B|3|0|I|F|0|0|N|6|1|9|4|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|23|8|@]|9|@$A|24|B|25|1|26]]|C|$]]|$1|D|3|E|5|F|7|27|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|28|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|29|8|@$A|2A|B|2B|M|N]]|9|@]|C|$]]|$1|O|3|P|5|6|7|2C|8|@]|9|@$A|2D|B|2E|1|2F]]|C|$]]|$1|Q|3|-4|5|6|7|2G|8|@]|9|@]|C|$]]|$1|R|3|S|5|6|7|2H|8|@$A|2I|B|2J|M|T]]|9|@]|C|$]]|$1|U|3|V|5|6|7|2K|8|@$A|2L|B|2M|M|N]]|9|@$A|2N|B|2O|1|2P]]|C|$]]|$1|W|3|X|5|6|7|2Q|8|@]|9|@]|C|$]]|$1|Y|3|Z|5|F|7|2R|8|@]|9|@]|C|$G|H]]|$1|10|3|11|5|6|7|2S|8|@$A|2T|B|2U|M|N]]|9|@]|C|$]]|$1|12|3|-4|5|6|7|2V|8|@]|9|@]|C|$]]|$1|13|3|14|5|6|7|2W|8|@$A|2X|B|2Y|M|N]|$A|2Z|B|30|M|T]]|9|@$A|31|B|32|1|33]]|C|$]]|$1|15|3|16|5|6|7|34|8|@$A|35|B|36|M|N]]|9|@]|C|$]]|$1|17|3|-4|5|6|7|37|8|@]|9|@]|C|$]]|$1|18|3|19|5|6|7|38|8|@$A|39|B|3A|M|N]]|9|@$A|3B|B|3C|1|3D]]|C|$]]|$1|1A|3|-4|5|6|7|3E|8|@]|9|@]|C|$]]|$1|1B|3|1C|5|1D|7|3F|8|@]|9|@]|C|$]]|$1|1E|3|-4|5|6|7|3G|8|@]|9|@]|C|$]]|$1|1F|3|1G|5|6|7|3H|8|@]|9|@]|C|$]]|$1|1H|3|1I|5|6|7|3I|8|@]|9|@]|C|$]]|$1|1J|3|1K|5|6|7|3J|8|@]|9|@]|C|$]]|$1|1L|3|1M|5|6|7|3K|8|@]|9|@]|C|$]]|$1|1N|3|-4|5|6|7|3L|8|@]|9|@]|C|$]]]|1O|$1P|$5|1Q|1R|1S|C|$1T|1U]]|1V|$5|1Q|1R|1S|C|$1T|1W]]|1X|$5|1Q|1R|1S|C|$1T|1Y]]|1Z|$5|1Q|1R|1S|C|$1T|20]]|21|$5|1Q|1R|1S|C|$1T|22]]]]

If you haven't pushed to origin yet, you can reset your branch to the <a href="https://stackoverflow.com/questions/2739376/definition-of-downstream-and-upstream/2749166#2749166">upstream</a> branch with:

<pre><code>git checkout mybranch
git reset --hard origin/mybranch
</code></pre>

(Make sure that you reference your latest commit in a separate branch, like you mention in your question)

Note that just after the reset, <code>mybranch@{1}</code> refers to the old commit, before reset.

But if you had already pushed, see "<a href="https://stackoverflow.com/a/773728/6309">Create git branch, and revert original to upstream state</a>" for other options.

<hr>

With Git 2.23 (August 2019), that would be one command: <a href="https://stackoverflow.com/a/57066202/6309"><code>git switch</code></a>. 
Namely: <a href="https://git-scm.com/docs/git-switch#Documentation/git-switch.txt--Cltnew-branchgt" rel="noreferrer"><code>git switch -C mybranch origin/mybranch</code></a>

Example

<pre><code>C:\Users\vonc\git\git&gt;git switch -C master origin/master
Reset branch 'master'
Branch 'master' set up to track remote branch 'master' from 'origin'.
Your branch is up to date with 'origin/master'.
</code></pre>

That restores the index and working tree, like a <code>git reset --hard</code> would.

<hr>

As commented by <a href="https://stackoverflow.com/users/259628/brad-herman">Brad Herman</a>, a <code>reset --hard</code> would remove any new file or reset modified file to HEAD. 

Actually, to be sure you start from a "clean slate", a <code>git clean -f -d</code> after the reset would ensure a working tree exactly identical to the branch you just reset to.

<hr>

This <a href="http://ocpsoft.org/tutorials/git/reset-and-sync-local-respository-with-remote-branch/" rel="noreferrer">blog post</a> suggests those aliases (for <code>master</code> branch only, but you can adapt/extend those):

<blockquote>
<pre><code>[alias]
 resetorigin = !git fetch origin &amp;&amp; git reset --hard origin/master &amp;&amp; git clean -f -d
 resetupstream = !git fetch upstream &amp;&amp; git reset --hard upstream/master &amp;&amp; git clean -f -d
</code></pre>
 
 Then you can type:

<pre><code>git resetupstream
</code></pre>
 
 or

<pre><code>git resetorigin
</code></pre>
</blockquote>

blocks|key|1615316|text|我在一台服务器上有一个私有存储库，并定期对其进行rebase/force-push，这使得我有必要经常在另一台计算机上重置本地分支。因此，我创建了以下别名"catchup"，它允许对当前分支执行此操作。与其他答案不同，此别名中没有硬编码的分支名称。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1615317|抓紧了。|1615318|[alias]
++catchup+=+"!f(){+echo+-n+\"reset+\\033[0;33m$(git+symbolic-ref+-q+--short+HEAD)\\033[0m+to+\\033[0;33m$(git+for-each-ref+--format='%25(upstream:short)'+$(git+symbolic-ref+-q+HEAD))\\033[0m?+(Y/n)+\";+read+-r+ans;+if+[+\"$ans\"+=+\"y\"+-o+\"$ans\"+=+\"Y\"+-o+-z+\"$ans\"+];+then+git+reset+--hard+$(git+for-each-ref+--format='%25(upstream:short)'+$(git+symbolic-ref+-q+HEAD));+else+echo+\"catchup+aborted\";+fi+};+f"|code-block|syntax|javascript|1615319|格式正确(不适用于.gitconfig中的换行符)如下所示：|1615320|"
!f(){
++echo+-n+\"reset+\\033[0;33m$(git+symbolic-ref+-q+--short+HEAD)\\033[0m+to+\\033[0;33m$(git+for-each-ref+--format='%25(upstream:short)'+$(git+symbolic-ref+-q+HEAD))\\033[0m?+(Y/n)+\";
++read+-r+ans;
++if+[+\"$ans\"+=+\"y\"+-o+\"$ans\"+=+\"Y\"+-o+-z+\"$ans\"+];+then
++++git+reset+--hard+$(git+for-each-ref+--format='%25(upstream:short)'+$(git+symbolic-ref+-q+HEAD));
++else
++++echo+\"catchup+aborted\";
++fi
};+f
"|1615321|带有color.|1615322|$(git+symbolic-ref+-q+--short+HEAD)的上游name|unordered-list-item|offset|length|style|CODE|1615323|
|1615324|$(git+for-each-ref+--format='%25(upstream:short)'+$(git+symbolic-ref+-q+HEAD))是当前分支的上游，|1615325|+\\033[0;33m和\\033[0m用于强调当前分支。|1615326|1615327|1615328|由于reset是一个潜在的危险调用(特别是使用--hard选项，您将丢失所有未提交的更改)，因此它首先告诉您它要做什么。例如，如果您在远程名为qcpp/dev-container的分支dev-container上，并输入git+catchup，系统将提示您：|1615329|1615330|将dev-container重置为qcpp/dev-container？(Y/n)|blockquote|1615331|1615332|1615333|如果您随后键入y或仅按回车键，它将执行重置。如果您输入任何其他内容，则不会执行重置。|1615334|如果您希望超级安全，并以编程方式防止丢失未暂存/未提交的更改，您可以使用according+checks+for+diff-index进一步拉皮条以上的别名。|1615335|必须警告的是:如果您正在使用其他人基于的公共存储库，并且您需要这个别名you+are+doing+it+wrong™。|1615336|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/3878624/how-do-i-programmatically-determine-if-there-are-uncommited-changes|1|https://git-scm.com/book/en/v2/Git-Branching-Rebasing#The-Perils-of-Rebasing^0|0|0|0|0|0|0|0|Z|0|0|0|24|0|1|B|D|8|0|0|0|32|B|0|0|0|0|0|0|10|V|0|0|Z|N|1|0^^$0|@$1|2|3|4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1S|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1T|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|1U|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|1V|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|1W|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|1X|8|@$R|1Y|S|1Z|T|U]]|9|@]|A|$]]|$1|V|3|W|5|6|7|20|8|@]|9|@]|A|$]]|$1|X|3|Y|5|Q|7|21|8|@$R|22|S|23|T|U]]|9|@]|A|$]]|$1|Z|3|10|5|Q|7|24|8|@$R|25|S|26|T|U]|$R|27|S|28|T|U]]|9|@]|A|$]]|$1|11|3|-4|5|6|7|29|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|2A|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|2B|8|@$R|2C|S|2D|T|U]]|9|@]|A|$]]|$1|15|3|-4|5|6|7|2E|8|@]|9|@]|A|$]]|$1|16|3|17|5|18|7|2F|8|@]|9|@]|A|$]]|$1|19|3|-4|5|6|7|2G|8|@]|9|@]|A|$]]|$1|1A|3|-4|5|6|7|2H|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|2I|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|2J|8|@]|9|@$R|2K|S|2L|1|2M]]|A|$]]|$1|1F|3|1G|5|6|7|2N|8|@]|9|@$R|2O|S|2P|1|2Q]]|A|$]]|$1|1H|3|-4|5|6|7|2R|8|@]|9|@]|A|$]]]|1I|$1J|$5|1K|1L|1M|A|$1N|1O]]|1P|$5|1K|1L|1M|A|$1N|1Q]]]]

I have a private repo on a server and regularly rebase/force-push to it, which makes it necessary to reset the local branch on my other computer often. I therefore created the following alias "catchup", which allows doing this for the current branch. Unlike the other answer there is no hardcoded branch name in this alias.

Hold on tight.

<pre><code>[alias]
 catchup = "!f(){ echo -n \"reset \\033[0;33m$(git symbolic-ref -q --short HEAD)\\033[0m to \\033[0;33m$(git for-each-ref --format='%(upstream:short)' $(git symbolic-ref -q HEAD))\\033[0m? (Y/n) \"; read -r ans; if [ \"$ans\" = \"y\" -o \"$ans\" = \"Y\" -o -z \"$ans\" ]; then git reset --hard $(git for-each-ref --format='%(upstream:short)' $(git symbolic-ref -q HEAD)); else echo \"catchup aborted\"; fi }; f"
</code></pre>

Properly formatted (won't work with the newlines in .gitconfig) it looks like this:

<pre><code>"
!f(){
 echo -n \"reset \\033[0;33m$(git symbolic-ref -q --short HEAD)\\033[0m to \\033[0;33m$(git for-each-ref --format='%(upstream:short)' $(git symbolic-ref -q HEAD))\\033[0m? (Y/n) \";
 read -r ans;
 if [ \"$ans\" = \"y\" -o \"$ans\" = \"Y\" -o -z \"$ans\" ]; then
 git reset --hard $(git for-each-ref --format='%(upstream:short)' $(git symbolic-ref -q HEAD));
 else
 echo \"catchup aborted\";
 fi
}; f
"
</code></pre>

<ul>
<li>The <code>\\033[0;33m</code> and <code>\\033[0m</code> is for emphasizing the current branch and upstream with color.</li>
<li><code>$(git symbolic-ref -q --short HEAD)</code> is the current branch name</li>
<li><code>$(git for-each-ref --format='%(upstream:short)' $(git symbolic-ref -q HEAD))</code> is the upstream of the current branch.</li>
</ul>

Since reset is a potentially dangerous call (especially with the --hard option, you will lose any uncommitted changes), it first tells you what it's about to do. For example if you're on branch dev-container with remote called qcpp/dev-container and you enter <code>git catchup</code>, you'll be prompted: 

<blockquote>
 reset dev-container to qcpp/dev-container? (Y/n)
</blockquote>

If you then type y or just hit return, it will perform the reset. If you enter anything else the reset will not be carried out.

If you want to be super safe and programmatically prevent losing unstaged/uncommitted changes, you can pimp the above alias further with <a href="https://stackoverflow.com/questions/3878624/how-do-i-programmatically-determine-if-there-are-uncommited-changes">according checks for diff-index</a>.

The obligatory word of warning: If you are working on a public repository other people have based work on, and you need this alias, <a href="https://git-scm.com/book/en/v2/Git-Branching-Rebasing#The-Perils-of-Rebasing" rel="noreferrer">you are doing it wrong™</a>.

blocks|key|726364|text|假设发生的是这样的情况：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|726365|#+on+branch+master
vi+buggy.py+++++++++++++++++#+you+edit+file
git+add+buggy.py++++++++++++#+stage+file
git+commit+-m+"Fix+the+bug"+#+commit
vi+tests.py+++++++++++++++++#+edit+another+file+but+do+not+commit+yet|code-block|syntax|javascript|726366|然后你会意识到你在错误的分支上做了改变。|726367|git+checkout+-b+mybranch++++#+you+create+the+correct+branch+and+switch+to+it|726368|但是master仍然指向你的提交。你想让它指向之前指向的地方。|offset|length|style|CODE|726369|解决方案|726370|最简单的方法是：|726371|git+branch+--force+master+origin/master|726372|另一种方式是：|726373|git+checkout+master
git+reset+--soft+origin/master
git+checkout+mybranch|726374|请注意，使用reset+--hard将导致未提交的更改丢失(在我的示例中为tests.py)。|726375|entityMap^0|0|0|0|0|2|6|0|0|0|0|0|0|6|C|11|8|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|16|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|17|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|18|8|@$M|19|N|1A|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1C|8|@]|9|@]|A|$]]|$1|U|3|V|5|D|7|1D|8|@]|9|@]|A|$E|F]]|$1|W|3|X|5|6|7|1E|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|D|7|1F|8|@]|9|@]|A|$E|F]]|$1|10|3|11|5|6|7|1G|8|@$M|1H|N|1I|O|P]|$M|1J|N|1K|O|P]]|9|@]|A|$]]|$1|12|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]]|13|$]]

Assuming this is what happened:

<pre><code># on branch master
vi buggy.py # you edit file
git add buggy.py # stage file
git commit -m "Fix the bug" # commit
vi tests.py # edit another file but do not commit yet
</code></pre>

Then you realise you make changes on the wrong branch.

<pre><code>git checkout -b mybranch # you create the correct branch and switch to it
</code></pre>

But <code>master</code> still points to your commit. You want it to point where it pointed before.

<h2>Solution</h2>

The easiest way is:

<pre><code>git branch --force master origin/master
</code></pre>

Another way is:

<pre><code>git checkout master
git reset --soft origin/master
git checkout mybranch
</code></pre>

Note that using <code>reset --hard</code> will cause your uncommitted changes to be lost (<code>tests.py</code> in my example).

blocks|key|595286|text|我试过了，它没有将我当前的分支重置为我最新的远程github。我在谷歌上找到了https://itsyndicate.org/blog/how-to-use-git-force-pull-properly/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|595287|这表明|595288|git+fetch+origin+master
git+reset+--hard+origin/master|code-block|syntax|javascript|595289|我想重置我的v8分支，所以我这样做了|595290|git+fetch+origin+v8
git+reset+--hard+origin/v8|595291|而且它起作用了|595292|entityMap|0|LINK|mutability|MUTABLE|url|https://itsyndicate.org/blog/how-to-use-git-force-pull-properly/^0|13|1S|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|13|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|14|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|15|8|@]|9|@]|C|$I|J]]|$1|O|3|P|5|6|7|16|8|@]|9|@]|C|$]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]]]

I tried this and it didn't reset my current branch to my remote github latest.
I googled and found 
<a href="https://itsyndicate.org/blog/how-to-use-git-force-pull-properly/" rel="noreferrer">https://itsyndicate.org/blog/how-to-use-git-force-pull-properly/</a>

which suggested

<pre><code>git fetch origin master
git reset --hard origin/master
</code></pre>

I wanted to reset my v8 branch so I did

<pre><code>git fetch origin v8
git reset --hard origin/v8
</code></pre>

and it worked

blocks|key|1611117|text|有一种更简单的方法可以做到这一点：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1611118|git+reset+--hard+@{u}|code-block|syntax|javascript|1611119|无论你的跟踪分支是什么，@{u}都是一个快捷方式，所以如果你在master上跟踪origin/master，@{u}会指向origin/master。|offset|length|style|CODE|1611120|使用它的好处是，您不必记住(或键入)跟踪分支的全名。您还可以创建别名：|1611121|git-reset-origin="git+reset+--hard+@{u}"|1611122|无论您当前所在的分支是什么，它都可以工作。|1611123|entityMap^0|0|0|C|4|V|6|14|D|1I|4|1P|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]|$I|Z|J|10|K|L]|$I|11|J|12|K|L]|$I|13|J|14|K|L]|$I|15|J|16|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|18|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|T|$]]

There is a slightly easier way to do this:
<pre><code>git reset --hard @{u}
</code></pre>
<code>@{u}</code> is a shortcut for whatever your tracking branch is, so if you're on <code>master</code> and that tracks <code>origin/master</code>, <code>@{u}</code> points to <code>origin/master</code>.
The advantage of using this is that you don't have to remember (or type out) the full name of your tracking branch. You can also make an alias:
<pre><code>git-reset-origin=&quot;git reset --hard @{u}&quot;
</code></pre>
which will work regardless of the branch you're currently on.

I was accidentally working on a branch I shouldn't have been for a while, so I branched off of it giving it the appropriate name. Now I want to overwrite the branch I shouldn't have been on to the version from origin (github). Is there an easy way to do this? I tried deleting the branch and then resetting up the tracking branch, but it just gives me the version I was working on again.

Need to reset git branch to origin version

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我无意中使用了一个我不应该有一段时间的分支，所以我将其分支，并给它起了一个合适的名称。现在，我想要覆盖我不应该从原始版本(github)开始的分支。有什么简单的方法可以做到这一点吗？我尝试删除分支，然后重新设置跟踪分支，但它只是给出了我再次处理的版本。

问需要将git分支重置为原始版本
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问需要将git分支重置为原始版本EN