From c3df1568712d6e1830b47a413d83631060564b7f Mon Sep 17 00:00:00 2001 From: Emmanuel Arias Date: Wed, 28 Jun 2023 06:56:19 -0300 Subject: [PATCH] Clarify the use of --amend (#354) Co-authored-by: Richard Littauer --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4b07d0a..22be15e 100644 --- a/README.md +++ b/README.md @@ -625,7 +625,7 @@ This tells rebase that you want to edit your third last commit and keep the othe (your-branch)$ git commit --amend ``` -which tells Git to recreate the commit, but to leave the commit message unedited. Having done that, the hard part is solved. +which tells Git to recreate the commit. Also, Git will ask you to write a new commit message, using the original commit message as a starting point. Having done that, the hard part is solved. ```sh (your-branch)$ git rebase --continue