|
|
@@ -399,8 +399,8 @@ However, be aware that in our PR workflow, we favor commits that bring the
|
|
|
codebase from one functional state to another functional state, without having
|
|
|
intermediate commits fixing up bugs in your own code or style issues. Most of
|
|
|
the time, we will prefer a single commit in a given PR (unless there's a good
|
|
|
-reason to keep the changes separate), so instead of authoring a new commit,
|
|
|
-considering using ``git commit --amend`` to amend the previous commit with your
|
|
|
+reason to keep the changes separate). Instead of authoring a new commit,
|
|
|
+consider using ``git commit --amend`` to amend the previous commit with your
|
|
|
fixes. The above example would then become:
|
|
|
|
|
|
::
|
TomBCodes