blocks|key|2999369|text|如果还没有人拉出您的远程repo，您可以更改分支头并强制将其推送到所述远程repo：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2999370|git+reset+--hard+HEAD%5E+
git+push+-f+|code-block|syntax|javascript|2999371|(或者，如果您可以直接访问远程存储库，则可以更改其HEAD+reference+even+though+it+is+a+bare+repo)|offset|length|2999372|请注意，正如alien-technology在the+comments+below中所评论的那样，在Windows+(CMD+session)上，您将需要%5E%5E|style|CODE|2999373|git+reset+--hard+HEAD%5E%5E
git+push+-f+|2999374|然后呢？正如Jon+Schneider在the+comments中指出的那样|2999375|2999376|如果带有"HEAD%5E“的命令导致error+no+matches+found:+HEAD%5E，请参见"git+show+HEAD%5E+doesn't+seem+to+be+working.+Is+this+normal?”|blockquote|2999377|2999378|2999379|自2011年以来的更新：|2999380|使用git+push+--force-with-lease+(that+I+present+here，2013年在Git1.8.5中引入)更安全。|BOLD|2999381|有关说明，请参阅Schwern的answer。|2999382|2999383|2999384|如果有人已经取消了回购怎么办？那我该怎么办呢？|2999385|2999386|2999387|然后我会建议一些不会重写历史的东西：|2999388|在本地恢复上一次提交(创建一个新的提交，该提交与上一次提交相反)推送由git+revert.生成的“|2999389|”|unordered-list-item|2999390|2999391|2999392|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/4624881/how-can-i-uncommit-the-last-commit-in-a-git-bare-repository/4625424#4625424|1|https://stackoverflow.com/users/1116812/alien-technology|2|https://stackoverflow.com/questions/4647301/rolling-back-local-and-remote-git-repository-by-1-commit/4647362#comment64375482_4647362|3|https://stackoverflow.com/users/12484/jon-schneider|4|https://stackoverflow.com/questions/4647301/rolling-back-local-and-remote-git-repository-by-1-commit/4647362?noredirect=1#comment122971508_4647362|5|https://stackoverflow.com/q/6091827/6309|6|https://stackoverflow.com/a/52937476/6309|7|https://stackoverflow.com/users/14660/schwern|8|https://stackoverflow.com/a/59994138/6309^0|0|0|P|18|0|0|25|2|6|G|1|N|I|2|0|0|6|D|3|K|C|4|0|0|5|5|G|T|1E|E|1E|1M|5|0|0|0|0|2|R|2|R|V|J|6|0|8|7|7|G|6|8|0|0|0|0|0|0|0|Z|A|0|0|0|0^^$0|@$1|2|3|4|5|6|7|28|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|29|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|2A|8|@]|9|@$I|2B|J|2C|1|2D]]|A|$]]|$1|K|3|L|5|6|7|2E|8|@$I|2F|J|2G|M|N]]|9|@$I|2H|J|2I|1|2J]|$I|2K|J|2L|1|2M]]|A|$]]|$1|O|3|P|5|D|7|2N|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|2O|8|@]|9|@$I|2P|J|2Q|1|2R]|$I|2S|J|2T|1|2U]]|A|$]]|$1|S|3|-4|5|6|7|2V|8|@]|9|@]|A|$]]|$1|T|3|U|5|V|7|2W|8|@$I|2X|J|2Y|M|N]|$I|2Z|J|30|M|N]|$I|31|J|32|M|N]]|9|@$I|33|J|34|1|35]]|A|$]]|$1|W|3|-4|5|6|7|36|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|37|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|38|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|39|8|@$I|3A|J|3B|M|12]|$I|3C|J|3D|M|N]]|9|@$I|3E|J|3F|1|3G]]|A|$]]|$1|13|3|14|5|6|7|3H|8|@]|9|@$I|3I|J|3J|1|3K]|$I|3L|J|3M|1|3N]]|A|$]]|$1|15|3|-4|5|6|7|3O|8|@]|9|@]|A|$]]|$1|16|3|-4|5|6|7|3P|8|@]|9|@]|A|$]]|$1|17|3|18|5|V|7|3Q|8|@]|9|@]|A|$]]|$1|19|3|-4|5|6|7|3R|8|@]|9|@]|A|$]]|$1|1A|3|-4|5|6|7|3S|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|3T|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|3U|8|@$I|3V|J|3W|M|N]]|9|@]|A|$]]|$1|1F|3|1G|5|1H|7|3X|8|@]|9|@]|A|$]]|$1|1I|3|-4|5|1H|7|3Y|8|@]|9|@]|A|$]]|$1|1J|3|-4|5|6|7|3Z|8|@]|9|@]|A|$]]|$1|1K|3|-4|5|6|7|40|8|@]|9|@]|A|$]]]|1L|$1M|$5|1N|1O|1P|A|$1Q|1R]]|1S|$5|1N|1O|1P|A|$1Q|1T]]|1U|$5|1N|1O|1P|A|$1Q|1V]]|1W|$5|1N|1O|1P|A|$1Q|1X]]|1Y|$5|1N|1O|1P|A|$1Q|1Z]]|20|$5|1N|1O|1P|A|$1Q|21]]|22|$5|1N|1O|1P|A|$1Q|23]]|24|$5|1N|1O|1P|A|$1Q|25]]|26|$5|1N|1O|1P|A|$1Q|27]]]]

If nobody has pulled your remote repo yet, you can change your branch HEAD and force push it to said remote repo:
<pre><code>git reset --hard HEAD^ 
git push -f 
</code></pre>
(or, if you have direct access to the remote repo, you can change its <a href="https://stackoverflow.com/questions/4624881/how-can-i-uncommit-the-last-commit-in-a-git-bare-repository/4625424#4625424">HEAD reference even though it is a bare repo</a>)
Note, as commented by <a href="https://stackoverflow.com/users/1116812/alien-technology">alien-technology</a> in <a href="https://stackoverflow.com/questions/4647301/rolling-back-local-and-remote-git-repository-by-1-commit/4647362#comment64375482_4647362">the comments below</a>, on Windows (CMD session), you would need <code>^^</code>:
<pre><code>git reset --hard HEAD^^
git push -f 
</code></pre>
And? as noted in <a href="https://stackoverflow.com/questions/4647301/rolling-back-local-and-remote-git-repository-by-1-commit/4647362?noredirect=1#comment122971508_4647362">the comments</a> by <a href="https://stackoverflow.com/users/12484/jon-schneider">Jon Schneider</a>:
<blockquote>
If the command with &quot;<code>HEAD^</code>&quot; results in <code>error no matches found: HEAD^</code>, see &quot;<a href="https://stackoverflow.com/q/6091827/6309"><code>git show HEAD^</code> doesn't seem to be working. Is this normal?</a>&quot;
</blockquote>
Update since 2011: 
Using <code>git push --force-with-lease</code> (<a href="https://stackoverflow.com/a/52937476/6309">that I present here</a>, introduced in 2013 with Git 1.8.5) is safer.
See <a href="https://stackoverflow.com/users/14660/schwern">Schwern</a>'s <a href="https://stackoverflow.com/a/59994138/6309">answer</a> for illustration.
<hr />
<blockquote>
What if somebody has already pulled the repo? What would I do then?
</blockquote>
Then I would suggest something that doesn't rewrite the history:
<ul>
<li><a href="http://www.kernel.org/pub/software/scm/git/docs/git-revert.html" rel="noreferrer"><code>git revert</code></a> locally your last commit (creating a new commit that reverses what the previous commit did)</li>
<li>push the 'revert' generated by <code>git revert</code>.</li>
</ul>

blocks|key|282958|text|将本地分支设置为后退一个版本(HEAD%5E表示后退一个版本)：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|282959|git+reset+--hard+HEAD%5E|code-block|syntax|javascript|282960|将更改推送到原点：|282961|git+push+--force|282962|你将不得不强制推送，因为否则git会识别出你落后于origin一次提交，并且什么都不会改变。|282963|使用--force可以让git覆盖远程存储库中的HEAD，而不考虑那里的任何改进。|282964|entityMap^0|F|5|0|0|0|0|P|6|0|2|7|O|4|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|13|8|@$9|14|A|15|B|C]|$9|16|A|17|B|C]]|D|@]|E|$]]|$1|S|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|T|$]]

Set the local branch one revision back (<code>HEAD^</code> means one revision back):

<pre><code>git reset --hard HEAD^
</code></pre>

Push the changes to origin:

<pre><code>git push --force
</code></pre>

You will have to force pushing because otherwise git would recognize that you're behind <code>origin</code> by one commit and nothing will change.

Doing it with <code>--force</code> tells git to overwrite <code>HEAD</code> in the remote repo without respecting any advances there.

blocks|key|285234|text|如果您可以直接访问远程存储库，则可以始终使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|285235|git+reset+--soft+HEAD%5E|code-block|syntax|javascript|285236|这是因为不会尝试修改不存在的工作目录。更多详情请参考原始答案：|285237|How+can+I+uncommit+the+last+commit+in+a+git+bare+repository?|offset|length|285238|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 HEAD^
</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|2999476|text|如果您想还原上次提交，请听：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2999477|步骤1：|2999478|使用消息检查您的本地提交|2999479|$+git+log|code-block|syntax|javascript|2999480|第2步：|2999481|删除上次提交，而不重置本地分支(或主分支)中的更改|2999482|$+git+reset+HEAD%5E|2999483|或者，如果您不希望上次提交文件和更新侦听|2999484|$+git+reset+HEAD%5E+--hard|2999485|第3步：|2999486|我们可以更新文件和代码，并再次需要强制推送，它将删除以前的提交。它将保持新提交。|2999487|$+git+push+origin+branch+-f|2999488|就这样!|2999489|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|15|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|16|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|17|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|18|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|19|8|@]|9|@]|A|$]]|$1|O|3|P|5|H|7|1A|8|@]|9|@]|A|$I|J]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@]|A|$]]|$1|S|3|T|5|H|7|1C|8|@]|9|@]|A|$I|J]]|$1|U|3|V|5|6|7|1D|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1E|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|H|7|1F|8|@]|9|@]|A|$I|J]]|$1|10|3|11|5|6|7|1G|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|13|$]]

If you want revert last commit listen:

Step 1:

Check your local commits with messages 

<pre><code>$ git log
</code></pre>

Step 2:

Remove last commit without resetting the changes from local branch (or master)

<pre><code>$ git reset HEAD^
</code></pre>

OR if you don't want last commit files and updates listens

<pre><code>$ git reset HEAD^ --hard
</code></pre>

Step 3:

We can update the files and codes and again need to push with force it will delete previous commit. It will keep new commit.

<pre><code>$ git push origin branch -f
</code></pre>

That's it!

blocks|key|282992|text|对于Windows计算机，请使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|282993|git+reset+HEAD~1++#Remove+Commit+Locally|code-block|syntax|javascript|282994|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

For Windows Machines, use:

<pre><code>git reset HEAD~1 #Remove Commit Locally
</code></pre>

blocks|key|2999514|text|我用下面的命令解决了像你这样的问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2999515|git+reset+--hard+HEAD%5E
git+push+-f+<remote>+<local+branch>:<remote+branch>+|code-block|syntax|javascript|2999516|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I solved problem like yours by this commands:

<pre><code>git reset --hard HEAD^
git push -f &lt;remote&gt; &lt;local branch&gt;:&lt;remote branch&gt; 
</code></pre>

blocks|key|283009|text|我只想从远程删除最后一次提交，并清除提交历史。下面的方法效果很好|type|unstyled|depth|inlineStyleRanges|entityRanges|data|283010|git+reset+--hard+HEAD%5E+
git+push+-f+|code-block|syntax|javascript|283011|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I just wanted to remove last commit from remote and clear commit history also.
The following worked like a charm

<pre><code>git reset --hard HEAD^ 
git push -f 
</code></pre>

blocks|key|2999551|text|重置磁头并恢复到上一次提交的方法是通过|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2999552|$+git+reset+HEAD%5E+--hard
$+git+push+<branchname>+-f|code-block|syntax|javascript|2999553|但有时它可能不会被远程分支接受：|2999554|To+ssh:<git+repo>
+!+[rejected]++++++++develop+->+develop+(non-fast-forward)
error:+failed+to+push+some+refs+to+'ssh:<git+repo>'
hint:+Updates+were+rejected+because+the+tip+of+your+current+branch+is+behind
hint:+its+remote+counterpart.+Integrate+the+remote+changes+(e.g.
hint:+'git+pull+...')+before+pushing+again.
hint:+See+the+'Note+about+fast-forwards'+in+'git+push+--help'+for+details.|2999555|那么另一种方法是|2999556|git+revert+HEAD
git+push+<remote+branch>|2999557|这可以很好地工作。|2999558|注意:请记住，如果git+push+-f+<force>失败，然后您尝试恢复。在此之前执行一次git+pull，以便远程和本地同步，然后尝试git+revert。|offset|length|style|CODE|2999559|请与git+log确认，以确保远程和本地在同一提交点具有相同的SHA1。|2999560|git+revert+
A+-->+B+-->+C+-->D
A-->+B+-->+C+-->+D+-->+%5ED(taking+out+the+changes+and+committing+reverted+diffs)|2999561|entityMap^0|0|0|0|0|0|0|0|9|J|1B|8|1Y|A|0|2|7|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|14|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|16|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|17|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|19|8|@$S|1A|T|1B|U|V]|$S|1C|T|1D|U|V]|$S|1E|T|1F|U|V]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1G|8|@$S|1H|T|1I|U|V]]|9|@]|A|$]]|$1|Y|3|Z|5|D|7|1J|8|@]|9|@]|A|$E|F]]|$1|10|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|11|$]]

The way to reset the head and do the revert to the previous commit is through 

<pre><code>$ git reset HEAD^ --hard
$ git push &lt;branchname&gt; -f
</code></pre>

But sometimes it might not be accepted in the remote branch: 

<pre><code>To ssh:&lt;git repo&gt;
 ! [rejected] develop -&gt; develop (non-fast-forward)
error: failed to push some refs to 'ssh:&lt;git repo&gt;'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
</code></pre>

then the other way to do is

<pre><code>git revert HEAD
git push &lt;remote branch&gt;
</code></pre>

This works fine.

NOTE: remember if the <code>git push -f &lt;force&gt;</code> failed and then you try to revert. Do a <code>git pull</code> before, so that remote and local are in sync and then try <code>git revert</code>. 
Check with <code>git log</code> to make sure the remote and local are at same point of commit with same SHA1..

<pre><code>git revert 
A --&gt; B --&gt; C --&gt;D
A--&gt; B --&gt; C --&gt; D --&gt; ^D(taking out the changes and committing reverted diffs)
</code></pre>

blocks|key|285296|text|在本地主机上|type|unstyled|depth|inlineStyleRanges|entityRanges|data|285297|git+reflog
--+this+will+list+all+last+commit
++e.g+Head@{0}+--+wrong+push
++++++Head@{1}+--+correct+push++
git+checkout+Head@{1}+.
++--+this+will+reset+your+last+modified+files

git+status+
git+commit+-m+"reverted+to+last+best"
git+push+origin/master|code-block|syntax|javascript|285298|不需要担心其他人是否已经退出。|285299|完成了！|285300|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|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

<h1>on local master</h1>

<pre><code>git reflog
-- this will list all last commit
 e.g Head@{0} -- wrong push
 Head@{1} -- correct push 
git checkout Head@{1} .
 -- this will reset your last modified files

git status 
git commit -m "reverted to last best"
git push origin/master
</code></pre>

No need to worry if other has pulled or not.

Done!

blocks|key|3212978|text|通过输入bellow命令，您可以查看您的git提交历史记录-|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3212979|$+git日志|offset|length|style|BOLD|3212980|假设您在该特定分支上的历史记录是-+commit_A，commit_B，commit_C，commit_D，其中，commit_D是最后一次提交，这是HEAD保留的位置。现在，要从本地和远程删除最后一次提交，您需要执行以下操作：|3212981|步骤1:通过以下方式在本地删除最后一次提交：|3212982|$+git重置--硬头~|3212983|这会将提交头更改为commit_C|3212984|第2步:将您的更改推送到远程|3212985|$+git推送原点%2B头部|3212986|此命令将从远程删除最后一次提交。|3212987|P.S.这个命令在Mac上测试过，应该也能在其他操作系统上运行(尽管不是关于其他操作系统的声明)|3212988|entityMap^0|0|2|5|0|0|0|2|A|0|0|0|2|A|0|0|0|1C|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@$D|11|E|12|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|14|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|15|8|@$D|16|E|17|F|G]]|9|@]|A|$]]|$1|N|3|O|5|6|7|18|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|19|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1A|8|@$D|1B|E|1C|F|G]]|9|@]|A|$]]|$1|T|3|U|5|6|7|1D|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1E|8|@$D|1F|E|1G|F|G]]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|Y|$]]

By entering bellow command you can see your git commit history -

$ git log

Let's say your history on that particular branch is like - 
commit_A, commit_B, commit_C, commit_D. Where, commit_D is the last commit and this is where HEAD remains. Now, to remove your last commit from local and remote, you need to do the following :

Step 1: Remove last commit locally by -

$ git reset --hard HEAD~

This will change your commit HEAD to commit_C

Step 2: Push your change for new HEAD commit to remote

$ git push origin +HEAD

This command will delete the last commit from remote.

P.S. this command is tested on Mac OSX and should work on other operating systems as well (not claiming about other OS though)

blocks|key|2999636|text|如果您只想从远程存储库中删除最后一次提交，而不想搞乱您的本地存储库，这里有一行代码：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2999637|git+push+origin+%2Borigin/master~:master|code-block|syntax|javascript|2999638|2999639|它使用以下语法：|2999640|git+push+<remote>+<refspec>|2999641|这里，<remote>是origin，<refspec>的结构如下：|offset|length|style|CODE|2999642|%2Borigin/master~:master|2999643|详细信息可以在git-push(1)中找到。前面的%2B表示“强制推送此ref"，另一部分表示”从origin/master~到master+(of+remote+origin)“。不难知道，origin/master~是origin/master之前的最后一个提交，对吧？|2999644|entityMap^0|0|0|0|0|0|3|8|C|6|J|9|0|0|7|B|P|1|1B|E|1Q|6|28|6|2M|E|31|D|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|L|3|M|5|6|7|12|8|@$N|13|O|14|P|Q]|$N|15|O|16|P|Q]|$N|17|O|18|P|Q]]|9|@]|A|$]]|$1|R|3|S|5|D|7|19|8|@]|9|@]|A|$E|F]]|$1|T|3|U|5|6|7|1A|8|@$N|1B|O|1C|P|Q]|$N|1D|O|1E|P|Q]|$N|1F|O|1G|P|Q]|$N|1H|O|1I|P|Q]|$N|1J|O|1K|P|Q]|$N|1L|O|1M|P|Q]|$N|1N|O|1O|P|Q]]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]]|W|$]]

If you only want to remove the last commit from the remote repository without messing up with your local repository, here's a one-liner:

<pre><code>git push origin +origin/master~:master
</code></pre>

<hr>

This uses the following syntax:

<pre><code>git push &lt;remote&gt; &lt;refspec&gt;
</code></pre>

Here, <code>&lt;remote&gt;</code> is <code>origin</code>, and <code>&lt;refspec&gt;</code> has the following structure:

<pre><code>+origin/master~:master
</code></pre>

Details can be found in <code>git-push(1)</code>. The preceding <code>+</code> means "force push this ref", and the other part means "from <code>origin/master~</code> to <code>master</code> (of remote <code>origin</code>)". It isn't hard to know that <code>origin/master~</code> is the last commit before <code>origin/master</code>, right?

blocks|key|3213021|text|这是一个更安全的过程的更新版本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3213022|git+reset+--hard+HEAD%5E+
git+push+--force-with-lease|code-block|syntax|javascript|3213023|git+push+-f将不加区别地用您自己的更改替换远程存储库。如果其他人推送了更改，这些更改将会丢失。只有当存储库如您所愿时，git+push+--force-with-lease才会推送您的rebase。如果其他人已经推送了，你的推送将会失败。|offset|length|style|CODE|3213024|参见–force+considered+harmful;+understanding+git’s+–force-with-lease。|3213025|我建议将其别名为repush+=+push+--force-with-lease。|3213026|3213027|如果有人已经取消了回购怎么办？那我该怎么办呢？|blockquote|3213028|3213029|3213030|告诉他们去找git+pull+--rebase=merges。它将使用git+fetch+origin和git+rebase+-r+origin/master，而不是git+fetch+origin和git+merge+origin/master。这将在新的重新建立基础的origin/master之上重写它们对master的任何本地更改。-r将保留他们可能进行的任何合并。|3213031|我建议将此设置为拉动的默认行为。它是安全的，将处理其他人的重定基数，并减少不必要的合并。|3213032|[pull]
++++++++rebase+=+merges|3213033|entityMap|0|LINK|mutability|MUTABLE|url|https://blog.developer.atlassian.com/force-with-lease/^0|0|0|0|B|1S|R|0|2|1S|0|0|8|W|0|0|0|0|0|6|O|Z|G|1G|R|2B|G|2S|N|3S|D|4C|6|4Q|2|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1B|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1C|8|@$I|1D|J|1E|K|L]|$I|1F|J|1G|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|1H|8|@]|9|@$I|1I|J|1J|1|1K]]|A|$]]|$1|O|3|P|5|6|7|1L|8|@$I|1M|J|1N|K|L]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|R|3|S|5|T|7|1P|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1S|8|@$I|1T|J|1U|K|L]|$I|1V|J|1W|K|L]|$I|1X|J|1Y|K|L]|$I|1Z|J|20|K|L]|$I|21|J|22|K|L]|$I|23|J|24|K|L]|$I|25|J|26|K|L]|$I|27|J|28|K|L]]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|29|8|@]|9|@]|A|$]]|$1|10|3|11|5|D|7|2A|8|@]|9|@]|A|$E|F]]|$1|12|3|-4|5|6|7|2B|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19]]]]

Here's an updated version of the procedure which is safer.

<pre><code>git reset --hard HEAD^ 
git push --force-with-lease
</code></pre>

<code>git push -f</code> will indiscriminately replace the remote repository with your own changes. If someone else has pushed changes they will be lost. <code>git push --force-with-lease</code> will only push your rebase if the repository is as you expect. If someone else has already pushed your push will fail.

See <a href="https://blog.developer.atlassian.com/force-with-lease/" rel="noreferrer">–force considered harmful; understanding git’s –force-with-lease</a>.

I recommend aliasing this as <code>repush = push --force-with-lease</code>.

<blockquote>
 What if somebody has already pulled the repo? What would I do then?
</blockquote>

Tell them to <code>git pull --rebase=merges</code>. Instead of a <code>git fetch origin</code> and <code>git merge origin/master</code> it will <code>git fetch origin</code> and <code>git rebase -r origin/master</code>. This will rewrite any of their local changes to <code>master</code> on top of the new rebased <code>origin/master</code>. <code>-r</code> will preserve any merges they may have made.

I recommend making this the default behavior for pulling. It is safe, will handle other's rebasing, and results in less unnecessary merges.

<pre><code>[pull]
 rebase = merges
</code></pre>

blocks|key|3213047|text|对我来说，这两个命令有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3213048|git+checkout+commit_id
git+push+origin+%2Bname_of_branch|code-block|syntax|javascript|3213049|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

for me works this two commands:

<pre><code>git checkout commit_id
git push origin +name_of_branch
</code></pre>

blocks|key|283079|text|您还可以执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|283080|git+reset+--hard+<commit-hash>
git+push+-f+origin+master|code-block|syntax|javascript|283081|并让其他所有收到最新错误提交的人重置：|283082|git+reset+--hard+origin/master|283083|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|$]]

You can also do this:

<pre><code>git reset --hard &lt;commit-hash&gt;
git push -f origin master
</code></pre>

and have everyone else who got the latest bad commits reset:

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

blocks|key|286355|text|有很多方法可以做到这一点。根据您的需求，从下面选择任何内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|286356|提交1.由REVERTing提交：|286357|如果您想恢复上次提交的所有更改，这意味着如果您在文件中添加了一些内容，这些内容将在恢复完成后被删除。如果您删除了文件中的某些内容，还原过程将添加这些文件。|286358|您可以还原最后一次提交。像这样：|286359|1.git+revert+head%5E
2.git+push+origin+<Branch-Name>|code-block|syntax|javascript|286360|或者，您可以使用该commit.Like的散列恢复到以前的任何提交：|286361|1.git+revert+<SHA>
2.git+push+origin++<Branch-Name>|286362|2.作者:+RESETing+previous+Head|offset|length|style|BOLD|286363|如果您只想指向以前的任何提交，请使用reset；它会将您的本地环境指向以前的提交。您可以将头部重置为以前的提交，或将头部重置为先前的任何提交。|286364|重置为以前的提交。|286365|1.git+reset+head%5E
2.git+push+-f+origin+<Branch-name>|286366|重置为以前的任何提交：|286367|1.git+reset+<SHA>
2.git+push+-f+origin+<Branch-name>|286368|在恢复和重置之间的权衡：|286369|为什么要选择恢复而不是重置操作？如果您已经将提交链推送到远程存储库(在远程存储库，其他人可能已经提取了您的代码并开始使用它)，那么恢复是取消对它们的更改的更好方法。这是因为Git工作流可以很好地处理分支末尾的额外提交，但是当有人重新设置分支指针时，如果链中不再出现一组提交，这将是一个挑战。|286370|entityMap^0|0|0|0|0|0|0|0|0|S|0|0|0|0|0|0|0|C|0|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1D|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1E|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1F|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|1G|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1H|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|1I|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|1J|8|@$S|1K|T|1L|U|V]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1M|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1N|8|@]|9|@]|A|$]]|$1|10|3|11|5|J|7|1O|8|@]|9|@]|A|$K|L]]|$1|12|3|13|5|6|7|1P|8|@]|9|@]|A|$]]|$1|14|3|15|5|J|7|1Q|8|@]|9|@]|A|$K|L]]|$1|16|3|17|5|6|7|1R|8|@$S|1S|T|1T|U|V]]|9|@]|A|$]]|$1|18|3|19|5|6|7|1U|8|@]|9|@]|A|$]]|$1|1A|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]]|1B|$]]

There are many way you can do this. Based on your requirement choose anything from below.
1. By REVERTing commit:
If you want to REVERT all the changes from you last COMMIT that means If you ADD something in your file that will be REMOVED after revert has been done. If you REMOVE something in your file the revert process will ADD those file.
You can REVERT the very last COMMIT. Like:
<pre><code>1.git revert head^
2.git push origin &lt;Branch-Name&gt;
</code></pre>
Or you can revert to any previous commit using the hash of that commit.Like:
<pre><code>1.git revert &lt;SHA&gt;
2.git push origin &lt;Branch-Name&gt;
</code></pre>
2. By RESETing previous Head
If you want to just point to any previous commit use reset; it points your local environment back to a previous commit. You can reset your head to previous commit or reset your head to previous any commit.
Reset to previous commit.
<pre><code>1.git reset head^
2.git push -f origin &lt;Branch-name&gt;
</code></pre>
Reset to any previous commit:
<pre><code>1.git reset &lt;SHA&gt;
2.git push -f origin &lt;Branch-name&gt;
</code></pre>
Trade of between REVERT &amp; RESET:
Why would you choose to do a revert over a reset operation? If you have already pushed your chain of commits to the remote repository (where others may have pulled your code and started working with it), a revert is a nicer way to cancel out changes for them. This is because the Git workflow works well for picking up additional commits at the end of a branch, but it can be challenging if a set of commits is no longer seen in the chain when someone resets the branch pointer back.

I've read the similar posts on this topic, and can't for the life of me figure out how to do this properly.

I checked in about 1000 files that I don't want, and I'd rather not have to go through 1by1 and remove them all from the repo.

<ul>
<li>I have a remote <code>master</code> Branch.</li>
<li>I have the local <code>master</code> Branch.</li>
</ul>

They are both at the same revision.

I want to rollback my remote by 1 commit.

Say my history on <code>master</code> is <code>A--B--C--D--E</code>. 
I want to rollback my local to <code>D</code>. 
Then push it to remote so my current hash will be D both remote and local. 

I'm having issues doing this. 
I'm using Git Tower but am comfortable with the command line. Any help?

UPDATE: 
Great comments below. Using a reset seems to be partially discouraged especially if the repository is shared with other users.
What's the best way to undo the previous commit's changes without using a hard reset? Is there a way?

Rolling back local and remote git repository by 1 commit

我已经读过关于这个主题的类似帖子，但我无论如何也想不出如何正确地做到这一点。我检入了大约1000个我不需要的文件，我不希望通过1by1将它们全部从存储库中删除。我有一个远程master分支。我有本地分支。它们都在同一版本中。我想通过1次提交回滚我的遥控器。假设我在master上的历史是A--B--C--D--E。我想将...

问1次提交回滚本地和远程git仓库
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问1次提交回滚本地和远程git仓库EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问1次提交回滚本地和远程git仓库
EN