blocks|key|808915|text|如果您要修复的提交不是最新的提交：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|808916|808917|git+rebase+--interactive+$parent_of_flawed_commit|ordered-list-item|offset|length|style|CODE|808918|808919|如果你想修复几个有缺陷的提交，请传递其中最老的一个的父级。|808920|编辑器将弹出一个列表，列出自你提交以来的所有提交。|unordered-list-item|808921|808922|1.+Change+`pick`+to+`reword`+(or+on+old+versions+of+Git,+to+`edit`)+in+front+of+any+commits+you+want+to+fix.
2.+Once+you+save,+Git+will+replay+the+listed+commits.+|code-block|syntax|javascript|808923|​|808924|808925|对于你想要改写的每次提交，Git都会把你放回你的编辑器中。对于您想要编辑的每个提交，Git都会将您放入shell。如果你在shell中：|808926|808927|1.+Change+the+commit+in+any+way+you+like.
2.+`git+commit+--amend`
3.+`git+rebase+--continue`|808928|808929|这个序列的大部分内容将在您执行过程中通过各种命令的输出向您解释。这非常简单；你不需要记住它--只要记住git+rebase+--interactive可以让你纠正提交，无论它们是在多长时间之前。|808930|808931|请注意，您不希望更改已经推送的提交。也许你是这样做的，但在这种情况下，你将不得不非常小心地与可能拉出你的提交并在其上完成工作的每个人进行沟通。|808932|entityMap^0|0|0|0|1D|0|0|0|0|0|0|0|0|0|0|0|0|1F|O|0|0|0^^$0|@$1|2|3|4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1D|8|@$F|1E|G|1F|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1H|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|1I|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|1K|8|@]|9|@]|A|$T|U]]|$1|V|3|W|5|6|7|1L|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|E|7|1N|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|11|3|12|5|S|7|1P|8|@]|9|@]|A|$T|U]]|$1|13|3|W|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|1R|8|@$F|1S|G|1T|H|I]]|9|@]|A|$]]|$1|16|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]|$1|17|3|18|5|6|7|1V|8|@]|9|@]|A|$]]|$1|19|3|-4|5|6|7|1W|8|@]|9|@]|A|$]]]|1A|$]]

If the commit you want to fix isn’t the most recent one:

<ol>
<li><code>git rebase --interactive $parent_of_flawed_commit</code>

If you want to fix several flawed commits, pass the parent of the oldest one of them.</li>
<li>An editor will come up, with a list of all commits since the one you gave.

<ol>
<li>Change <code>pick</code> to <code>reword</code> (or on old versions of Git, to <code>edit</code>) in front of any commits you want to fix.</li>
<li>Once you save, Git will replay the listed commits. </li>
</ol></li>
<li>For each commit you want to reword, Git will drop you back into your editor. For each commit you want to edit, Git drops you into the shell. If you’re in the shell:

<ol>
<li>Change the commit in any way you like.</li>
<li><code>git commit --amend</code></li>
<li><code>git rebase --continue</code></li>
</ol></li>
</ol>

Most of this sequence will be explained to you by the output of the various commands as you go. It’s very easy; you don’t need to memorise it – just remember that <code>git rebase --interactive</code> lets you correct commits no matter how long ago they were.

<hr>

Note that you will not want to change commits that you have already pushed. Or maybe you do, but in that case you will have to take great care to communicate with everyone who may have pulled your commits and done work on top of them. <a href="https://stackoverflow.com/questions/4084868/how-do-i-recover-resynchronise-after-someone-pushes-a-rebase-or-a-reset-to-a-pub">How do I recover/resynchronise after someone pushes a rebase or a reset to a published branch?</a>

blocks|key|5359182|text|修改最新的提交消息|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5359183|git+commit+--amend|code-block|syntax|javascript|5359184|将打开您的编辑器，允许您更改最近提交的提交消息。此外，您还可以在命令行中使用以下命令直接设置提交消息：|5359185|git+commit+--amend+-m+"New+commit+message"|5359186|…但是，这可能会使多行提交消息或小更正输入起来更加麻烦。|5359187|在执行此操作之前，请确保您没有任何工作副本更改，否则它们也会被提交。(未暂存的更改将不会提交。)|5359188|更改已推送到远程分支的提交消息|5359189|如果您已经将提交推送到远程分支，那么在本地修改提交之后(如上所述)，您还将使用以下命令执行need+to+force+push+the+commit：|offset|length|5359190|git+push+<remote>+<branch>+--force
#+Or
git+push+<remote>+<branch>+-f|5359191|警告:强制推送会用本地one的状态覆盖远程分支。如果远程分支上有您在本地分支中没有的提交，那么您将丢失这些提交。|style|BOLD|5359192|警告:修改你已经与其他人共享的提交时要小心。修改提交本质上是将它们重写为具有不同的SHA+ID，如果其他人拥有你重写的旧提交的副本，这将带来问题。任何拥有旧提交副本的人都需要将他们的工作与新重写的提交同步，这有时可能很困难，因此在尝试重写共享提交历史时，请确保与其他人协调，或者只是避免完全重写共享提交。|5359193|5359194|执行交互式rebase|5359195|另一种选择是使用交互式rebase。这允许您编辑任何想要更新的邮件，即使它不是最新的邮件。|5359196|要执行Git压缩，请执行以下步骤：|5359197|//+n+is+the+number+of+commits+up+to+the+last+commit+you+want+to+be+able+to+edit
git+rebase+-i+HEAD~n|5359198|压缩提交后-选择用于编辑消息的e/r：|CODE|5359199|​|5359200|📷|atomic|5359201|5359202|关于交互式rebase的重要说明|5359203|当您使用git+rebase+-i+HEAD~n时，可能会有比n个提交更多的提交()。Git将“收集”最近n个提交中的所有提交，如果在该范围内的某个地方存在合并，您也会看到所有提交，因此结果将是n%2B。|5359204|小贴士：|5359205|如果您必须为多个分支执行此操作，并且在修改内容时可能会遇到冲突，请设置git+rerere并让Git自动为您解决这些冲突。|5359206|5359207|文档|5359208|5359209|git-commit(1)+Manual+Page|unordered-list-item|5359210|5359211|5359212|git-rebase(1)+Manual+Page|5359213|5359214|5359215|git-push(1)+Manual+Page|5359216|5359217|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/41003071/why-must-i-force-push-after-changing-a-commit-message|1|http://en.wikipedia.org/wiki/SHA-1|2|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/100ba2b4c2630f4e6cca4e8f3fac7bf7.png|imageAlt|3|https://stackoverflow.com/questions/35415925/is-it-possible-to-setup-git-merge-for-automatic-resolving-git-rerere/35417944#35417944|4|https://www.kernel.org/pub/software/scm/git/docs/git-commit.html|5|https://www.kernel.org/pub/software/scm/git/docs/git-rebase.html|6|https://www.kernel.org/pub/software/scm/git/docs/git-push.html^0|0|0|0|0|0|0|0|19|T|0|0|0|0|E|0|0|M|15|3|1|0|0|0|0|0|0|F|3|0|0|0|1|2|0|0|0|4|K|0|0|Z|A|Z|A|3|0|0|0|0|0|P|4|0|0|0|0|P|5|0|0|0|0|N|6|0|0^^$0|@$1|2|3|4|5|6|7|2W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|2X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|2Y|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|2Z|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|30|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|31|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|32|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|33|8|@]|9|@$S|34|T|35|1|36]]|A|$]]|$1|U|3|V|5|D|7|37|8|@]|9|@]|A|$E|F]]|$1|W|3|X|5|6|7|38|8|@$S|39|T|3A|Y|Z]]|9|@]|A|$]]|$1|10|3|11|5|6|7|3B|8|@$S|3C|T|3D|Y|Z]]|9|@$S|3E|T|3F|1|3G]]|A|$]]|$1|12|3|-4|5|6|7|3H|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|3I|8|@]|9|@]|A|$]]|$1|15|3|16|5|6|7|3J|8|@]|9|@]|A|$]]|$1|17|3|18|5|6|7|3K|8|@]|9|@]|A|$]]|$1|19|3|1A|5|D|7|3L|8|@]|9|@]|A|$E|F]]|$1|1B|3|1C|5|6|7|3M|8|@$S|3N|T|3O|Y|1D]]|9|@]|A|$]]|$1|1E|3|1F|5|6|7|3P|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|1I|7|3Q|8|@]|9|@$S|3R|T|3S|1|3T]]|A|$]]|$1|1J|3|1F|5|6|7|3U|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|6|7|3V|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|6|7|3W|8|@$S|3X|T|3Y|Y|1D]]|9|@]|A|$]]|$1|1O|3|1P|5|6|7|3Z|8|@]|9|@]|A|$]]|$1|1Q|3|1R|5|6|7|40|8|@$S|41|T|42|Y|1D]]|9|@$S|43|T|44|1|45]]|A|$]]|$1|1S|3|-4|5|6|7|46|8|@]|9|@]|A|$]]|$1|1T|3|1U|5|6|7|47|8|@]|9|@]|A|$]]|$1|1V|3|-4|5|6|7|48|8|@]|9|@]|A|$]]|$1|1W|3|1X|5|1Y|7|49|8|@]|9|@$S|4A|T|4B|1|4C]]|A|$]]|$1|1Z|3|-4|5|6|7|4D|8|@]|9|@]|A|$]]|$1|20|3|-4|5|6|7|4E|8|@]|9|@]|A|$]]|$1|21|3|22|5|1Y|7|4F|8|@]|9|@$S|4G|T|4H|1|4I]]|A|$]]|$1|23|3|-4|5|6|7|4J|8|@]|9|@]|A|$]]|$1|24|3|-4|5|6|7|4K|8|@]|9|@]|A|$]]|$1|25|3|26|5|1Y|7|4L|8|@]|9|@$S|4M|T|4N|1|4O]]|A|$]]|$1|27|3|-4|5|6|7|4P|8|@]|9|@]|A|$]]|$1|28|3|-4|5|6|7|4Q|8|@]|9|@]|A|$]]]|29|$2A|$5|2B|2C|2D|A|$2E|2F]]|2G|$5|2B|2C|2D|A|$2E|2H]]|2I|$5|2J|2C|2K|A|$2L|2M|2N|-4]]|2O|$5|2B|2C|2D|A|$2E|2P]]|2Q|$5|2B|2C|2D|A|$2E|2R]]|2S|$5|2B|2C|2D|A|$2E|2T]]|2U|$5|2B|2C|2D|A|$2E|2V]]]]

<h1>Amending the most recent commit message</h1>
<pre class="lang-sh prettyprint-override"><code>git commit --amend
</code></pre>
will open your editor, allowing you to change the commit message of the most recent commit. Additionally, you can set the commit message directly in the command line with:
<pre class="lang-sh prettyprint-override"><code>git commit --amend -m &quot;New commit message&quot;
</code></pre>
…however, this can make multi-line commit messages or small corrections more cumbersome to enter.
Make sure you don't have any working copy changes staged before doing this or they will get committed too. (Unstaged changes will not get committed.)
<h2>Changing the message of a commit that you've already pushed to your remote branch</h2>
If you've already pushed your commit up to your remote branch, then - after amending your commit locally (as described above) - you'll also <a href="https://stackoverflow.com/questions/41003071/why-must-i-force-push-after-changing-a-commit-message">need to force push the commit</a> with:
<pre class="lang-bash prettyprint-override"><code>git push &lt;remote&gt; &lt;branch&gt; --force
# Or
git push &lt;remote&gt; &lt;branch&gt; -f
</code></pre>
Warning: force-pushing will overwrite the remote branch with the state of your local one. If there are commits on the remote branch that you don't have in your local branch, you will lose those commits.
Warning: be cautious about amending commits that you have already shared with other people. Amending commits essentially rewrites them to have different <a href="http://en.wikipedia.org/wiki/SHA-1" rel="noreferrer">SHA</a> IDs, which poses a problem if other people have copies of the old commit that you've rewritten. Anyone who has a copy of the old commit will need to synchronize their work with your newly re-written commit, which can sometimes be difficult, so make sure you coordinate with others when attempting to rewrite shared commit history, or just avoid rewriting shared commits altogether.
<hr />
<h3>Perform an interactive rebase</h3>
Another option is to use interactive rebase.
This allows you to edit any message you want to update even if it's not the latest message.
In order to do a Git squash, follow these steps:
<pre><code>// n is the number of commits up to the last commit you want to be able to edit
git rebase -i HEAD~n
</code></pre>
Once you squash your commits - choose the <code>e/r</code> for editing the message:
<a href="https://i.stack.imgur.com/LVcm9.png" rel="noreferrer"><img src="https://i.stack.imgur.com/LVcm9.png" alt="Enter image description here" /></a>
<h3>Important note about interactive rebase</h3>
When you use <code>git rebase -i HEAD~n</code> there can be more than n commits. Git will &quot;collect&quot; all the commits in the last n commits, and if there was a merge somewhere in between that range you will see all the commits as well, so the outcome will be n + .
<h3>Good tip:</h3>
If you have to do it for more than a single branch and you might face conflicts when amending the content, set up <a href="https://stackoverflow.com/questions/35415925/is-it-possible-to-setup-git-merge-for-automatic-resolving-git-rerere/35417944#35417944"><code>git rerere</code></a> and let Git resolve those conflicts automatically for you.
<hr />
<h2>Documentation</h2>
<ul>
<li><a href="https://www.kernel.org/pub/software/scm/git/docs/git-commit.html" rel="noreferrer">git-commit(1) Manual Page</a>
</li>
<li><a href="https://www.kernel.org/pub/software/scm/git/docs/git-rebase.html" rel="noreferrer">git-rebase(1) Manual Page</a>
</li>
<li><a href="https://www.kernel.org/pub/software/scm/git/docs/git-push.html" rel="noreferrer">git-push(1) Manual Page</a>
</li>
</ul>

blocks|key|3949451|text|git+commit+--amend+-m+"your+new+message"|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|3949452|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre class="lang-sh prettyprint-override"><code>git commit --amend -m "your new message"
</code></pre>

blocks|key|5359524|text|如前所述，git+commit+--amend是覆盖最后一次提交的方法。注意:如果您还想用覆盖文件，则命令为|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|5359525|git+commit+-a+--amend+-m+"My+new+commit+message"|code-block|syntax|javascript|5359526|entityMap^0|5|I|19|4|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|D]]|E|@]|F|$]]|$1|G|3|H|5|I|7|S|8|@]|E|@]|F|$J|K]]|$1|L|3|-4|5|6|7|T|8|@]|E|@]|F|$]]]|M|$]]

As already mentioned, <code>git commit --amend</code> is the way to overwrite the last commit. One note: if you would like to also overwrite the files, the command would be 

<pre class="lang-c prettyprint-override"><code>git commit -a --amend -m "My new commit message"
</code></pre>

blocks|key|3103914|text|您也可以使用git+filter-branch来实现这一点。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3103915|git+filter-branch+-f+--msg-filter+"sed+'s/errror/error/'"+$flawed_commit..HEAD|code-block|syntax|javascript|3103916|它不像简单的git+commit+--amend那么简单，但是如果在错误的提交消息之后已经有了一些合并，那么它就特别有用。|3103917|注意，这将尝试重写HEAD和有缺陷的提交之间的每个提交，因此您应该非常明智地选择您的msg-filter命令;-)|3103918|entityMap^0|6|H|0|0|6|I|0|9|4|16|A|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|P|$]]

You also can use <code>git filter-branch</code> for that.

<pre class="lang-c prettyprint-override"><code>git filter-branch -f --msg-filter "sed 's/errror/error/'" $flawed_commit..HEAD
</code></pre>

It's not as easy as a trivial <code>git commit --amend</code>, but it's especially useful, if you already have some merges after your erroneous commit message.

Note that this will try to rewrite every commit between <code>HEAD</code> and the flawed commit, so you should choose your <code>msg-filter</code> command very wisely ;-)

blocks|key|3103952|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3103953|如果只想修改最后一条提交消息，请执行以下操作：|ordered-list-item|3103954|3103955|git提交--修改|3103956|这将使您进入文本编辑器，并允许您更改最后一条提交消息。|3103957|3103958|如果您想要更改最后三个提交消息或任何提交消息，请为git+rebase+-i命令提供HEAD~3：|offset|length|style|CODE|3103959|3103960|git+rebase+-i+HEAD~3|3103961|entityMap^0|0|0|0|0|0|0|P|D|16|6|0|0|0^^$0|@$1|2|3|-4|4|5|6|U|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|V|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|W|7|@]|8|@]|9|$]]|$1|E|3|F|4|5|6|X|7|@]|8|@]|9|$]]|$1|G|3|H|4|5|6|Y|7|@]|8|@]|9|$]]|$1|I|3|-4|4|5|6|Z|7|@]|8|@]|9|$]]|$1|J|3|K|4|C|6|10|7|@$L|11|M|12|N|O]|$L|13|M|14|N|O]]|8|@]|9|$]]|$1|P|3|-4|4|5|6|15|7|@]|8|@]|9|$]]|$1|Q|3|R|4|5|6|16|7|@]|8|@]|9|$]]|$1|S|3|-4|4|5|6|17|7|@]|8|@]|9|$]]]|T|$]]

<ol>
<li>If you only want to modify your last commit message, then do:

<pre><code>git commit --amend
</code></pre></li>
</ol>

That will drop you into your text editor and let you change the last commit message.

<ol start="2">
<li>If you want to change the last three commit messages, or any of the commit messages up to that point, supply <code>HEAD~3</code> to the <code>git rebase -i</code> command:

<pre><code>git rebase -i HEAD~3
</code></pre></li>
</ol>

blocks|key|3104052|text|如果您使用的是Git+GUI工具，则有一个名为“修改上次提交”的按钮。单击该按钮，然后它将显示您上次提交的文件和消息。只需编辑该消息，即可使用新提交消息提交该消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3104053|或者从控制台/终端使用以下命令：|3104054|git+commit+-a+--amend+-m+"My+new+commit+message"|code-block|syntax|javascript|3104055|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

If you are using the Git GUI tool, there is a button named Amend last commit. Click on that button and then it will display your last commit files and message. Just edit that message, and you can commit it with a new commit message.

Or use this command from a console/terminal:

<pre><code>git commit -a --amend -m "My new commit message"
</code></pre>

blocks|key|3104111|text|如果您必须在多个分支上更改旧的提交消息(即，带有错误消息的提交存在于多个分支中)，您可能希望使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3104112|git+filter-branch+-f+--msg-filter+\
'sed+"s/<old+message>/<new+message>/g"'+--+--all|code-block|syntax|javascript|3104113|Git将创建一个临时目录，用于重写和备份refs/original/中的旧引用。|offset|length|style|CODE|3104114|3104115|-f将强制执行该操作。如果临时目录已经存在，或者在refs/original下已经存储了引用，则需要执行此操作。如果不是这样，您可以删除此flag.|unordered-list-item|3104116|--分隔筛选器-分支选项与修订options.|3104117|--all将确保重写所有分支和标签。|3104118|3104119|由于备份了旧的引用，您可以轻松地返回到执行该命令之前的状态。|3104120|比方说，您想要恢复主服务器并在分支old_master中访问它|3104121|git+checkout+-b+old_master+refs/original/refs/heads/master|3104122|entityMap^0|0|0|K|E|0|0|0|2|P|D|0|0|2|0|0|5|0|0|0|H|A|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|14|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|15|8|@$I|16|J|17|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|19|8|@$I|1A|J|1B|K|L]|$I|1C|J|1D|K|L]]|9|@]|A|$]]|$1|Q|3|R|5|P|7|1E|8|@$I|1F|J|1G|K|L]]|9|@]|A|$]]|$1|S|3|T|5|P|7|1H|8|@$I|1I|J|1J|K|L]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1L|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1M|8|@$I|1N|J|1O|K|L]]|9|@]|A|$]]|$1|Z|3|10|5|D|7|1P|8|@]|9|@]|A|$E|F]]|$1|11|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|12|$]]

If you have to change an old commit message over multiple branches (i.e., the commit with the erroneous message is present in multiple branches) you might want to use:

<pre class="lang-bash prettyprint-override"><code>git filter-branch -f --msg-filter \
'sed "s/&lt;old message&gt;/&lt;new message&gt;/g"' -- --all
</code></pre>

Git will create a temporary directory for rewriting and additionally backup old references in <code>refs/original/</code>.

<ul>
<li><code>-f</code> will enforce the execution of the operation. This is necessary if the temporary directory is already present or if there are already references stored under <code>refs/original</code>. If that is not the case, you can drop this flag.</li>
<li><code>--</code> separates filter-branch options from revision options.</li>
<li><code>--all</code> will make sure that all branches and tags are rewritten.</li>
</ul>

Due to the backup of your old references, you can easily go back to the state before executing the command.

Say, you want to recover your master and access it in branch <code>old_master</code>:

<pre><code>git checkout -b old_master refs/original/refs/heads/master
</code></pre>

blocks|key|5359841|text|如果您使用的是Git+GUI，则可以使用以下命令修改尚未推送的最后一次提交：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5359842|Commit/Amend+Last+Commit|code-block|syntax|javascript|5359843|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|$]]

If you are using the Git GUI, you can amend the last commit which hasn't been pushed with: 

<pre><code>Commit/Amend Last Commit
</code></pre>

blocks|key|3104221|text|我更喜欢这样：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3104222|git+commit+--amend+-c+<commit+ID>|code-block|syntax|javascript|3104223|否则，将使用新的提交ID进行新的提交。|3104224|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|$]]

I prefer this way:

<pre><code>git commit --amend -c &lt;commit ID&gt;
</code></pre>

Otherwise, there will be a new commit with a new commit ID.

blocks|key|5359947|text|修改|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5359948|这里有几个选项。你可以做到|5359949|git+commit+--amend|code-block|syntax|javascript|5359950|只要这是你的最后一次提交。|5359951|交互式重定库|5359952|否则，如果这不是您的最后一次提交，您可以进行交互式rebase，|5359953|git+rebase+-i+[branched_from]+[hash+before+commit]|5359954|然后，在交互式rebase中，您只需将编辑添加到该提交。当它出现时，执行git+commit+--amend并修改提交消息。如果希望在提交点之前回滚，也可以使用git+reflog并删除该提交。然后你只需要再做一次git+commit。|offset|length|style|CODE|5359955|entityMap^0|0|0|0|0|0|0|0|10|I|28|A|2Z|A|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|15|8|@$S|16|T|17|U|V]|$S|18|T|19|U|V]|$S|1A|T|1B|U|V]]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|X|$]]

<h3>Amend</h3>

You have a couple of options here. You can do

<pre><code>git commit --amend
</code></pre>

as long as it's your last commit.

<h3>Interactive rebase</h3>

Otherwise, if it's not your last commit, you can do an interactive rebase,

<pre><code>git rebase -i [branched_from] [hash before commit]
</code></pre>

Then inside the interactive rebase you simply add edit to that commit. When it comes up, do a <code>git commit --amend</code> and modify the commit message. If you want to roll back before that commit point, you could also use <code>git reflog</code> and just delete that commit. Then you just do a <code>git commit</code> again.

blocks|key|809302|text|您可以使用Git+rebasing。例如，如果要修改回提交bbc643cd，请运行|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|809303|$+git+rebase+bbc643cd%5E+--interactive|code-block|syntax|javascript|809304|在默认编辑器中，将您想要修改其提交的行中的'pick‘修改为'edit’。进行更改，然后使用|809305|$+git+add+<filepattern>|809306|现在您可以使用|809307|$+git+commit+--amend|809308|修改提交，并在此之后|809309|$+git+rebase+--continue|809310|返回到前一次头提交。|809311|entityMap|0|LINK|mutability|MUTABLE|url|http://git-scm.com/book/en/Git-Branching-Rebasing^0|5|C|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|F|7|18|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|19|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|1A|8|@]|9|@]|C|$G|H]]|$1|M|3|N|5|6|7|1B|8|@]|9|@]|C|$]]|$1|O|3|P|5|F|7|1C|8|@]|9|@]|C|$G|H]]|$1|Q|3|R|5|6|7|1D|8|@]|9|@]|C|$]]|$1|S|3|T|5|F|7|1E|8|@]|9|@]|C|$G|H]]|$1|U|3|V|5|6|7|1F|8|@]|9|@]|C|$]]|$1|W|3|-4|5|6|7|1G|8|@]|9|@]|C|$]]]|X|$Y|$5|Z|10|11|C|$12|13]]]]

You can use <a href="http://git-scm.com/book/en/Git-Branching-Rebasing">Git rebasing</a>. For example, if you want to modify back to commit bbc643cd, run

<pre><code>$ git rebase bbc643cd^ --interactive
</code></pre>

In the default editor, modify 'pick' to 'edit' in the line whose commit you want to modify. Make your changes and then stage them with

<pre><code>$ git add &lt;filepattern&gt;
</code></pre>

Now you can use

<pre><code>$ git commit --amend
</code></pre>

to modify the commit, and after that

<pre><code>$ git rebase --continue
</code></pre>

to return back to the previous head commit.

blocks|key|3104387|text|使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3104388|git+commit+--amend|code-block|syntax|javascript|3104389|要详细了解它，一个很好的帖子是。它还讨论了不使用+git+commit+--amend时的。|offset|length|style|CODE|BOLD|3104390|entityMap^0|0|0|P|I|19|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Q|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|R|8|@$I|S|J|T|K|L]|$I|U|J|V|K|M]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

Use

<pre><code>git commit --amend
</code></pre>

To understand it in detail, an excellent post is <a href="https://www.atlassian.com/git/tutorials/rewriting-history#git-commit--amend" rel="noreferrer">4. Rewriting Git History</a>. It also talks about when not to use <code>git commit --amend</code>.

blocks|key|3104476|text|我尽可能多地使用Git+GUI，这为您提供了修改上次提交的选项：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3104477|​|3104478|📷|atomic|3104479|3104480|此外，git+rebase+-i+origin/master是一个很好的咒语，它将始终向您呈现您在master上所做的提交，并为您提供修改、删除、重新排序或压缩的选项。不需要先获取散列。|style|CODE|3104481|entityMap|0|LINK|mutability|MUTABLE|url|http://git-scm.com/docs/git-gui|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/30f780530bd7caa7d460331dace163c7.png|imageAlt^0|8|7|0|0|0|0|1|1|0|0|3|R|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@$A|12|B|13|1|14]]|C|$]]|$1|D|3|E|5|6|7|15|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|16|8|@]|9|@$A|17|B|18|1|19]]|C|$]]|$1|I|3|E|5|6|7|1A|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|1B|8|@$A|1C|B|1D|L|M]]|9|@]|C|$]]|$1|N|3|-4|5|6|7|1E|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]|V|$5|W|R|X|C|$Y|Z|10|-4]]]]

I use the <a href="http://git-scm.com/docs/git-gui">Git GUI</a> as much as I can, and that gives you the option to amend the last commit:

<img src="https://i.stack.imgur.com/qXMzu.png" alt="Tick that box" title="Check that box &quot;Amend Last Commit&quot;!">

Also, <code>git rebase -i origin/master</code>is a nice mantra that will always present you with the commits you have done on top of master, and give you the option to amend, delete, reorder or squash. No need to get hold of that hash first.

blocks|key|5360145|text|哇，所以有很多方法可以做到这一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5360146|另一种方法是删除最后一次提交，但保留它的更改，这样您就不会丢失工作。然后，您可以对更正后的消息执行另一次提交。这看起来像这样：|5360147|git+reset+--soft+HEAD~1
git+commit+-m+'New+and+corrected+commit+message'|code-block|syntax|javascript|5360148|如果我忘记添加文件或进行更改，我总是这样做。|5360149|记住指定--soft而不是--hard，否则将完全丢失提交。|offset|length|style|BOLD|CODE|5360150|entityMap^0|0|0|0|0|0|2|4|6|D|6|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|V|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|W|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|X|8|@$M|Y|N|Z|O|P]|$M|10|N|11|O|Q]|$M|12|N|13|O|Q]]|9|@]|A|$]]|$1|R|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|S|$]]

Wow, so there are a lot of ways to do this.

Yet another way to do this is to delete the last commit, but keep its changes so that you won't lose your work. You can then do another commit with the corrected message. This would look something like this:

<pre class="lang-bash prettyprint-override"><code>git reset --soft HEAD~1
git commit -m 'New and corrected commit message'
</code></pre>

I always do this if I forget to add a file or do a change.

Remember to specify <code>--soft</code> instead of <code>--hard</code>, otherwise you lose that commit entirely.

blocks|key|5360165|text|我已经为recommit+(amend)+it添加了别名reci和recm。现在我可以用git+recm或git+recm+-m来做了|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5360166|$+vim+~/.gitconfig

[alias]

++++......
++++cm+=+commit
++++reci+=+commit+--amend
++++recm+=+commit+--amend
++++......|code-block|syntax|javascript|5360167|entityMap^0|4|G|S|4|X|4|18|8|1H|B|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|L|$]]

I have added the aliases <code>reci</code> and <code>recm</code> for <code>recommit (amend)</code> it. Now I can do it with <code>git recm</code> or <code>git recm -m</code>:

<pre><code>$ vim ~/.gitconfig

[alias]

 ......
 cm = commit
 reci = commit --amend
 recm = commit --amend
 ......
</code></pre>

blocks|key|805075|text|如果您只想编辑最新的提交，请使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|805076|git+commit+--amend|code-block|syntax|javascript|805077|或|805078|git+commit+--amend+-m+'one+line+message'|805079|但是如果你想在一行中编辑多个提交，你应该改用rebasing：|805080|git+rebase+-i+<hash+of+one+commit+before+the+wrong+commit>|805081|​|805082|📷|atomic|offset|length|805083|805084|在像上面这样的文件中，编写edit/e或其他选项之一，然后点击保存并退出。|style|CODE|805085|现在你将在第一个错误的提交。在文件中进行更改，它们将自动为您暂存。类型|805086|git+commit+--amend|805087|保存并退出该文件，然后键入|805088|git+rebase+--continue|805089|移动到下一个选择，直到完成所有选择。|805090|请注意，在该特定提交之后，这些内容会更改所有的SHA散列。|805091|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/79905cc42f6bfc08cc8af19a31a63ec8.png|imageAlt^0|0|0|0|0|0|0|0|0|1|0|0|0|D|6|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1L|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1M|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1N|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|1O|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|1P|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|1Q|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|1R|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|1S|8|@]|9|@$T|1T|U|1U|1|1V]]|A|$]]|$1|V|3|P|5|6|7|1W|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1X|8|@$T|1Y|U|1Z|Y|Z]]|9|@]|A|$]]|$1|10|3|11|5|6|7|20|8|@]|9|@]|A|$]]|$1|12|3|13|5|D|7|21|8|@]|9|@]|A|$E|F]]|$1|14|3|15|5|6|7|22|8|@]|9|@]|A|$]]|$1|16|3|17|5|D|7|23|8|@]|9|@]|A|$E|F]]|$1|18|3|19|5|6|7|24|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|25|8|@]|9|@]|A|$]]|$1|1C|3|-4|5|6|7|26|8|@]|9|@]|A|$]]]|1D|$1E|$5|1F|1G|1H|A|$1I|1J|1K|-4]]]]

If you just want to edit the latest commit, use:

<pre><code>git commit --amend
</code></pre>

or

<pre class="lang-bash prettyprint-override"><code>git commit --amend -m 'one line message'
</code></pre>

But if you want to edit several commits in a row, you should use rebasing instead:

<pre><code>git rebase -i &lt;hash of one commit before the wrong commit&gt;
</code></pre>

<img src="https://i.stack.imgur.com/jRTRr.png" alt="Git rebase editing">

In a file, like the one above, write <code>edit/e</code> or one of the other options, and hit save and exit.

Now you'll be at the first wrong commit. Make changes in the files, and they'll be automatically staged for you. Type

<pre><code>git commit --amend
</code></pre>

Save and exit that and type

<pre><code>git rebase --continue
</code></pre>

to move to next selection until finished with all your selections.

Note that these things change all your SHA hashes after that particular commit.

blocks|key|5360281|text|使用一行中的新提交消息更新上一条错误提交消息：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5360282|git+commit+--amend+-m+"your+new+commit+message"|code-block|syntax|javascript|5360283|或者，尝试Git+reset，如下所示：|5360284|#+You+can+reset+your+head+to+n+number+of+commit
#+NOT+a+good+idea+for+changing+last+commit+message,
#+but+you+can+get+an+idea+to+split+commit+into+multiple+commits
git+reset+--soft+HEAD%5E

#+It+will+reset+you+last+commit.+Now,+you
#+can+re-commit+it+with+new+commit+message.|5360285|使用reset将提交拆分为更小的提交|5360286|git+reset还可以帮助您将一个提交分解为多个提交：|offset|length|style|CODE|5360287|#+Reset+your+head.+I+am+resetting+to+last+commits:
git+reset+--soft+HEAD%5E
#+(You+can+reset+multiple+commit+by+doing+HEAD~2(no.+of+commits)

#+Now,+reset+your+head+for+splitting+it+to+multiple+commits
git+reset+HEAD

#+Add+and+commit+your+files+separately+to+make+multiple+commits:+e.g
git+add+app/
git+commit+-m+"add+all+files+in+app+directory"

git+add+config/
git+commit+-m+"add+all+files+in+config+directory"|5360288|在这里，您已经成功地将最后一次提交分解为两次提交。|5360289|entityMap^0|0|0|0|0|0|0|9|0|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|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|13|8|@$O|14|P|15|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|D|7|16|8|@]|9|@]|A|$E|F]]|$1|U|3|V|5|6|7|17|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

Update your last wrong commit message with the new commit message in one line:

<pre class="lang-bash prettyprint-override"><code>git commit --amend -m "your new commit message"
</code></pre>

Or, try Git reset like below:

<pre class="lang-bash prettyprint-override"><code># You can reset your head to n number of commit
# NOT a good idea for changing last commit message,
# but you can get an idea to split commit into multiple commits
git reset --soft HEAD^

# It will reset you last commit. Now, you
# can re-commit it with new commit message.
</code></pre>

<h3>Using reset to split commits into smaller commits</h3>

<code>git reset</code> can help you to break one commit into multiple commits too:

<pre class="lang-bash prettyprint-override"><code># Reset your head. I am resetting to last commits:
git reset --soft HEAD^
# (You can reset multiple commit by doing HEAD~2(no. of commits)

# Now, reset your head for splitting it to multiple commits
git reset HEAD

# Add and commit your files separately to make multiple commits: e.g
git add app/
git commit -m "add all files in app directory"

git add config/
git commit -m "add all files in config directory"
</code></pre>

Here you have successfully broken your last commit into two commits.

blocks|key|3104750|text|如果您只想更改最后一条消息，则应该在commit+--amend中使用--only标志或其快捷方式-o|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3104751|git+commit+--amend+-o+-m+"New+commit+message"|code-block|syntax|javascript|3104752|这可以确保您不会意外地使用分阶段的东西来增强提交。当然，最好是有一个适当的$EDITOR配置。然后，您可以省略-m选项，Git将用旧的提交消息预先填充提交消息。这样，就可以很容易地对其进行编辑。|3104753|entityMap^0|I|E|Z|6|1D|2|0|0|11|7|1J|2|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|N|$]]

If you only want to change your last message you should use the <code>--only</code> flag or its shortcut <code>-o</code> with <code>commit --amend</code>:

<pre class="lang-bash prettyprint-override"><code>git commit --amend -o -m "New commit message"
</code></pre>

This ensures that you don't accidentally enhance your commit with staged stuff. Of course it's best to have a proper <code>$EDITOR</code> configuration. Then you can leave the <code>-m</code> option out, and Git will pre-fill the commit message with the old one. In this way it can be easily edited.

blocks|key|3950574|text|我意识到我推入了一个有打字错误的提交。为了撤消，我执行了以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3950575|git+commit+--amend+-m+"T-1000,+advanced+prototype"
git+push+--force|code-block|syntax|javascript|3950576|警告：强制推送您的更改将用本地分支覆盖远程分支。确保你不会覆盖任何你想要保留的东西。如果其他任何人与您共享分支，也要小心强制推送修改(重写)的提交，因为如果他们拥有您刚刚重写的提交的旧副本，他们将需要重写自己的历史。|offset|length|style|BOLD|3950577|entityMap^0|0|0|0|3|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|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I realised that I had pushed a commit with a typo in it. In order to undo, I did the following:

<pre class="lang-bash prettyprint-override"><code>git commit --amend -m "T-1000, advanced prototype"
git push --force
</code></pre>

Warning: force pushing your changes will overwrite the remote branch with your local one. Make sure that you aren't going to be overwriting anything that you want to keep. Also be cautious about force pushing an amended (rewritten) commit if anyone else shares the branch with you, because they'll need to rewrite their own history if they have the old copy of the commit that you've just rewritten.

blocks|key|3105021|text|我喜欢使用以下几点：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3105022|3105023|git+status|ordered-list-item|offset|length|style|CODE|3105024|git+add+--all|3105025|git+commit+-am+"message+goes+here+about+the+change"|3105026|git+pull+<origin+master>|3105027|git+push+<origin+master>|3105028|3105029|entityMap^0|0|0|0|A|0|0|D|0|0|1F|0|0|O|0|0|O|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|W|8|@$F|X|G|Y|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|Z|8|@$F|10|G|11|H|I]]|9|@]|A|$]]|$1|L|3|M|5|E|7|12|8|@$F|13|G|14|H|I]]|9|@]|A|$]]|$1|N|3|O|5|E|7|15|8|@$F|16|G|17|H|I]]|9|@]|A|$]]|$1|P|3|Q|5|E|7|18|8|@$F|19|G|1A|H|I]]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|T|$]]

I like to use the following:

<ol>
<li><code>git status</code></li>
<li><code>git add --all</code></li>
<li><code>git commit -am "message goes here about the change"</code></li>
<li><code>git pull &lt;origin master&gt;</code></li>
<li><code>git push &lt;origin master&gt;</code></li>
</ol>

blocks|key|3950773|text|如果您尚未将代码推送到远程分支(GitHub/Bitbucket)，则可以在命令行上更改提交消息，如下所示。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3950774|+git+commit+--amend+-m+"Your+new+message"|code-block|syntax|javascript|3950775|如果您正在处理特定的分支，请执行以下操作：|3950776|git+commit+--amend+-m+"BRANCH-NAME:+new+message"|3950777|如果您已经使用错误的消息推送了代码，并且在更改消息时需要小心。也就是说，在您更改提交消息并尝试再次推送它之后，您最终会遇到问题。要使其平滑，请执行以下步骤。|3950778|在做之前，请阅读我的完整答案。|style|BOLD|3950779|git+commit+--amend+-m+"BRANCH-NAME+:+your+new+message"

git+push+-f+origin+BRANCH-NAME++++++++++++++++#+Not+a+best+practice.+Read+below+why?|3950780|重要提示：当您直接使用强制推送时，您可能会遇到其他开发人员正在处理同一分支的代码问题。因此，为了避免这些冲突，您需要在创建强制推送之前从分支中提取代码|3950781|+git+commit+--amend+-m+"BRANCH-NAME+:+your+new+message"
+git+pull+origin+BRANCH-NAME
+git+push+-f+origin+BRANCH-NAME|3950782|如果提交消息已经被推送，这是更改提交消息时的最佳实践。|3950783|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/GitHub|1|http://en.wikipedia.org/wiki/Bitbucket^0|G|6|0|N|9|1|0|0|0|0|0|0|F|0|0|0|5|1P|4|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@$A|1B|B|1C|1|1D]|$A|1E|B|1F|1|1G]]|C|$]]|$1|D|3|E|5|F|7|1H|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|1I|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|1J|8|@]|9|@]|C|$G|H]]|$1|M|3|N|5|6|7|1K|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|1L|8|@$A|1M|B|1N|Q|R]]|9|@]|C|$]]|$1|S|3|T|5|F|7|1O|8|@]|9|@]|C|$G|H]]|$1|U|3|V|5|6|7|1P|8|@$A|1Q|B|1R|Q|R]|$A|1S|B|1T|Q|R]]|9|@]|C|$]]|$1|W|3|X|5|F|7|1U|8|@]|9|@]|C|$G|H]]|$1|Y|3|Z|5|6|7|1V|8|@]|9|@]|C|$]]|$1|10|3|-4|5|6|7|1W|8|@]|9|@]|C|$]]]|11|$12|$5|13|14|15|C|$16|17]]|18|$5|13|14|15|C|$16|19]]]]

If you have not pushed the code to your remote branch (<a href="http://en.wikipedia.org/wiki/GitHub">GitHub</a>/<a href="http://en.wikipedia.org/wiki/Bitbucket">Bitbucket</a>) you can change the commit message on the command line as below.

<pre><code> git commit --amend -m "Your new message"
</code></pre>

If you're working on a specific branch do this:

<pre><code>git commit --amend -m "BRANCH-NAME: new message"
</code></pre>

If you've already pushed the code with the wrong message, and you need to be careful when changing the message. That is, after you change the commit message and try pushing it again, you end up with having issues. To make it smooth, follow these steps.

Please read my entire answer before doing it.

<pre><code>git commit --amend -m "BRANCH-NAME : your new message"

git push -f origin BRANCH-NAME # Not a best practice. Read below why?
</code></pre>

Important note: When you use the force push directly you might end up with code issues that other developers are working on the same branch. So to avoid those conflicts, you need to pull the code from your branch before making the force push:

<pre><code> git commit --amend -m "BRANCH-NAME : your new message"
 git pull origin BRANCH-NAME
 git push -f origin BRANCH-NAME
</code></pre>

This is the best practice when changing the commit message, if it was already pushed.

blocks|key|805345|text|您可以使用git-rebase-reword|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|805346|它的设计目的是以与commit+--amend相同的方式编辑任何提交(而不仅仅是最后一次)|style|CODE|805347|$+git+rebase-reword+<commit-or-refname>|code-block|syntax|javascript|805348|它是根据修改提交的rebase交互式操作命名的："reword“。请参阅this+post和man+-section交互模式-|805349|示例：|805350|$+git+rebase-reword+b68f560
$+git+rebase-reword+HEAD%5E|805351|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/albfan/git-rebase-reword|1|https://robots.thoughtbot.com/git-interactive-rebase-squash-amend-rewriting-history|2|http://git-scm.com/docs/git-rebase^0|5|H|0|0|9|E|0|0|10|9|1|1A|3|2|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|6|7|18|8|@$A|19|B|1A|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|1B|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1C|8|@]|9|@$A|1D|B|1E|1|1F]|$A|1G|B|1H|1|1I]]|C|$]]|$1|O|3|P|5|6|7|1J|8|@]|9|@]|C|$]]|$1|Q|3|R|5|J|7|1K|8|@]|9|@]|C|$K|L]]|$1|S|3|-4|5|6|7|1L|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]|10|$5|V|W|X|C|$Y|11]]|12|$5|V|W|X|C|$Y|13]]]]

You can use <a href="https://github.com/albfan/git-rebase-reword">git-rebase-reword</a>

It is designed to edit any commit (not just last) same way as <code>commit --amend</code>

<pre><code>$ git rebase-reword &lt;commit-or-refname&gt;
</code></pre>

It is named after the action on rebase interactive to amend a commit: "reword". See <a href="https://robots.thoughtbot.com/git-interactive-rebase-squash-amend-rewriting-history">this post</a> and <a href="http://git-scm.com/docs/git-rebase">man</a> -section interactive mode-

Examples:

<pre><code>$ git rebase-reword b68f560
$ git rebase-reword HEAD^
</code></pre>

I wrote the wrong thing in a commit message.

How can I change the message? The commit has not been pushed yet.

How to modify existing, unpushed commit messages?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我在提交消息中写错了东西。我怎样才能更改消息？提交尚未推送。

问如何修改现有的未推送的提交消息？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何修改现有的未推送的提交消息？EN