From 02d83f431527042686c5ab963eeb235f43ac48eb Mon Sep 17 00:00:00 2001 From: Emmanuel Arias Date: Sat, 17 Jun 2023 21:02:19 -0300 Subject: [PATCH] Clarify the use of --amend This commit try to clarify the use of --amend. Now it mentions that the command will ask for a commit message. Closes: #353 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4b07d0a..e40c1e6 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