Updated Developer Guide (markdown)
+1
-1
@@ -322,7 +322,7 @@ easily-understandable chunks. Any individual commit should not add more than
|
|||||||
one new class or one new function. Do not submit commits that change thousands
|
one new class or one new function. Do not submit commits that change thousands
|
||||||
of lines or that contain more than one distinct logical change. Trivial
|
of lines or that contain more than one distinct logical change. Trivial
|
||||||
commits, e.g. to fix lint errors, should be merged into the commit that
|
commits, e.g. to fix lint errors, should be merged into the commit that
|
||||||
introduced the error.
|
introduced the error. See the [Atomic Commit Convention on Wikipedia](http://en.wikipedia.org/wiki/Atomic_commit#Atomic_Commit_Convention) for more detail.
|
||||||
|
|
||||||
`git apply --patch` and `git rebase` can help you create a clean commit
|
`git apply --patch` and `git rebase` can help you create a clean commit
|
||||||
history.
|
history.
|
||||||
|
|||||||
Reference in New Issue
Block a user