CONTRIBUTING: mention not changing spelling/typoes in code

This commit is contained in:
moneromooo-monero 2018-12-03 19:07:59 +00:00
parent 58ce16d4d9
commit ea85de4f02
No known key found for this signature in database
GPG key ID: 686F07454D6CEFC3

View file

@ -19,7 +19,8 @@ posted to #monero-dev on irc.freenode.net).
Patches should be self contained. A good rule of thumb is to have Patches should be self contained. A good rule of thumb is to have
one patch per separate issue, feature, or logical change. Also, no one patch per separate issue, feature, or logical change. Also, no
other changes, such as random whitespace changes or reindentation. other changes, such as random whitespace changes, reindentation,
or fixing typoes, spelling, or wording, unless user visible.
Following the code style of the particular chunk of code you're Following the code style of the particular chunk of code you're
modifying is encouraged. Proper squashing should be done (eg, if modifying is encouraged. Proper squashing should be done (eg, if
you're making a buggy patch, then a later patch to fix the bug, you're making a buggy patch, then a later patch to fix the bug,