From c86e858454b9cadc2d47cd7039592e8d8ad5be82 Mon Sep 17 00:00:00 2001 From: Axel Navarro Date: Fri, 27 Sep 2024 11:32:08 -0300 Subject: [PATCH] Update 20.git-rebase-edit.md --- posts/navarroaxel/20.git-rebase-edit.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/posts/navarroaxel/20.git-rebase-edit.md b/posts/navarroaxel/20.git-rebase-edit.md index bcebac8..d6a5670 100644 --- a/posts/navarroaxel/20.git-rebase-edit.md +++ b/posts/navarroaxel/20.git-rebase-edit.md @@ -1,7 +1,7 @@ --- title: A step-by-step guide to splitting commits using Git rebase published: true -description: Learn why and how to split commits to keep your Git history clean and organized. Whether you're backporting hotfixes or simply aiming for more readable commit history, this step-by-step guide has got you covered. +description: Learn why and how to split commits to keep your Git history clean and organized. Whether you're backport hotfixes or simply aiming for more readable commit history, this step-by-step guide has got you covered. tags: 'git, bash, productivity, tooling' cover_image: ./assets/git-rebase-edit.png id: 2015782 @@ -45,7 +45,7 @@ git commit -m 'fix grid responsiveness' git rebase --continue ``` -Git will continue running the second `exec` command that makes an `npm test`. If this fails you will need to fix your code; otherwise Git will continue with the `break` command returning the control of the shell to you again. Here you are able to run your application, make the final checks, etc. +Git will continue running the second `exec` command that makes an `npm test`. If this fails you will need to fix your code; otherwise Git will stop at the `break` command returning the control of the shell to you again. Here you are able to run your application, make the final checks, etc. If you're happy with the changes, run `git rebase --continue` to finish the rebase, or `git rebase --abort` to cancel all changes. 👀