From 687dad2fac3e04694bae4558e5aa19ee07614df8 Mon Sep 17 00:00:00 2001 From: Piotr Gajowniczek Date: Mon, 29 Oct 2018 11:58:21 +0100 Subject: [PATCH] Update Git workflow 1.2 Make changes (#137) * Update Git workflow 1.2 Make changesi - Advise to use add --patch - Switch to use commit without --all * Fix space * Change usage for git add - Describe specifying file list - Include --patch as tip --- README.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 7878fe9..b4a933c 100644 --- a/README.md +++ b/README.md @@ -98,11 +98,18 @@ Because of most of the reasons above, we use [Feature-branch-workflow](https://w ``` * Make Changes. ```sh - git add - git commit -a + git add ... + git commit ``` _Why:_ - > `git commit -a` will start an editor which lets you separate the subject from the body. Read more about it in *section 1.3*. + > `git add ... ` - you should add only files that make up a small and coherent change. + + > `git commit` will start an editor which lets you separate the subject from the body. + + > Read more about it in *section 1.3*. + + _Tip:_ + > You could use `git add -p` instead, which will give you chance to review all of the introduced changes one by one, and decide whether to include them in the commit or not. * Sync with remote to get changes you’ve missed. ```sh