jimeh/common-flow
1
0
Fork 0
mirror of https://github.com/jimeh/common-flow.git synced 2026-02-19 01:16:40 +00:00
Code Issues Packages Projects Releases Wiki Activity

Swap order of "git add -i" and "git add -p"

Browse Source 
Using the -p option is a shorthand to get into the patch section of
interactive mode. Hence the -i option is the main one to use.
This commit is contained in:
Jim Myhrberg
2017-08-26 20:45:39 +01:00
parent 399c5bf27a
commit 045eded571
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
common-flow.md
View File

@@ -209,8 +209,9 @@ interpreted as described in [RFC 2119](https://tools.ietf.org/html/rfc2119).
documentation: documentation:
<https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project#_commit_guidelines> <https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project#_commit_guidelines>
2. You SHOULD never blindly commit all changes with "git commit -a". It is 2. You SHOULD never blindly commit all changes with "git commit -a". It is
RECOMMENDED you use "git add -p" or "git add -i" to add individual changes to the staging RECOMMENDED you use "git add -i" or "git add -p" to add individual
area so you are fully aware of what you are committing. changes to the staging area so you are fully aware of what you are
committing.
3. You SHOULD always use "--force-with-lease" when doing a force push. The 3. You SHOULD always use "--force-with-lease" when doing a force push. The
regular "--force" option is dangerous and destructive. More regular "--force" option is dangerous and destructive. More
information: information: