blocks|key|1617734|text|您可以对所有n次提交使用git+revert+<commit>…，然后像往常一样进行推送，保持历史记录不变。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1617735|或者你可以用git+reset+--hard+HEAD~n“回滚”。如果您正在推送公共或共享存储库，您可能会基于您的原始分支而分散并破坏其他工作。Git将阻止您这样做，但您可以使用git+push+-f来强制更新。|1617736|entityMap^0|C|K|0|6|N|2I|B|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

You can use <code>git revert &lt;commit&gt;…</code> for all the n commits, and then push as usual, keeping history unchanged.

Or you can "roll back" with <code>git reset --hard HEAD~n</code>. If you are pushing in a public or shared repository, you may diverge and break others work based on your original branch. Git will prevent you doing so, but you can use <code>git push -f</code> to force the update.

blocks|key|1403084|text|埃尔马科是对的..。他的建议对于共享/公共存储库(或者至少是公共分支)是最好的。如果它没有被分享(或者你愿意破坏其他人)，你也可以推送一个特定的ref：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1403085|git+push+origin+old_master:master|code-block|syntax|javascript|1403086|或者，如果有一个特定的提交SHA1+(比方说1e4f99e，缩写形式)，您想要移回：|1403087|git+push+origin+1e4f99e:master|1403088|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|$]]

elmarco is correct... his suggestion is the best for shared/public repositories (or, at least public branches). If it wasn't shared (or you're willing to disrupt others) you can also push a particular ref:

<pre><code>git push origin old_master:master
</code></pre>

Or, if there's a particular commit SHA1 (say 1e4f99e in abbreviated form) you'd like to move back to:

<pre><code>git push origin 1e4f99e:master
</code></pre>

blocks|key|1617860|text|如果您可以直接访问远程存储库，则可以始终使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1617861|git+reset+--soft+<sha1>|code-block|syntax|javascript|1617862|这是因为不会尝试修改不存在的工作目录。更多详情请参考原始答案：|1617863|How+can+I+uncommit+the+last+commit+in+a+git+bare+repository?|offset|length|1617864|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/4624881/how-can-i-uncommit-the-last-commit-in-a-git-bare-repository/5627799#5627799^0|0|0|0|0|1O|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|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@$K|Y|L|Z|1|10]]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

If you have direct access to the remote repo, you could always use:

<pre><code>git reset --soft &lt;sha1&gt;
</code></pre>

This works since there is no attempt to modify the non-existent working directory. For more details please see the original answer:

<a href="https://stackoverflow.com/questions/4624881/how-can-i-uncommit-the-last-commit-in-a-git-bare-repository/5627799#5627799">How can I uncommit the last commit in a git bare repository?</a>

blocks|key|1403167|text|幸运的是，我可以使用Pat+Notz's+solution，它完全消除了不需要的提交。然而，最初我得到了这个错误|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1403168|error:+failed+to+push+some+refs+to+'ssh://git@gitrepo.git'
To+prevent+you+from+losing+history,+non-fast-forward+updates+were+rejected*|code-block|syntax|javascript|1403169|但是添加force+(-f)选项会覆盖此错误|style|CODE|1403170|git+push+-f+origin+52e36b294e:master|1403171|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/588615/1828051^0|A|J|0|0|0|B|2|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|@$A|12|B|13|K|L]]|9|@]|C|$]]|$1|M|3|N|5|F|7|14|8|@]|9|@]|C|$G|H]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

Fortunately I was in a position to use <a href="https://stackoverflow.com/a/588615/1828051">Pat Notz's solution</a> which completely removed the unwanted commit. However, initially I got the error

<pre><code>error: failed to push some refs to 'ssh://git@gitrepo.git'
To prevent you from losing history, non-fast-forward updates were rejected*
</code></pre>

But adding the force (<code>-f</code>) option overwrite this error

<pre><code>git push -f origin 52e36b294e:master
</code></pre>

I have a remote Git repository, and I need to roll back the last <code>n</code> commits into cold oblivion.

Rolling back a remote Git repository

我有一个远程Git存储库，我需要将最后一次n提交回滚到冷遗忘中。

问回滚远程Git存储库
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问回滚远程Git存储库EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问回滚远程Git存储库
EN