diff options
| author | luigi1111 <luigi1111w@gmail.com> | 2018-12-31 15:36:03 -0600 |
|---|---|---|
| committer | luigi1111 <luigi1111w@gmail.com> | 2018-12-31 15:36:03 -0600 |
| commit | 8bfbb8d598b0b1468211b464950d9dda8f56beda (patch) | |
| tree | 6e66e14654b046b75b354b99135f144f4e126412 | |
| parent | Merge pull request #4933 (diff) | |
| parent | CONTRIBUTING: mention not changing spelling/typoes in code (diff) | |
| download | monero-8bfbb8d598b0b1468211b464950d9dda8f56beda.tar.xz | |
Merge pull request #4935
ea85de4 CONTRIBUTING: mention not changing spelling/typoes in code (moneromooo-monero)
| -rw-r--r-- | CONTRIBUTING.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3de9cd5ce..883d366aa 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -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 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 modifying is encouraged. Proper squashing should be done (eg, if you're making a buggy patch, then a later patch to fix the bug, |