Skip to content

Commit f195f84

Browse files
authored
Helping contributors. (simdjson#1289)
1 parent 669e5b9 commit f195f84

File tree

2 files changed

+9
-0
lines changed

2 files changed

+9
-0
lines changed

.github/pull_request_template.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
2+
3+
Our tests check whether you have introduced trailing white space. If such a test fails, please check the "artifacts button" above, which if you click it gives a link to a downloadable file to help you identify the issue. You can also run scripts/remove_trailing_whitespace.sh locally if you have a bash shell and the sed command available on your system.
4+
5+
If you plan to contribute to simdjson, please read our
6+
7+
CONTRIBUTING guide: https://github.com/simdjson/simdjson/blob/master/CONTRIBUTING.md and our
8+
HACKING guide: https://github.com/simdjson/simdjson/blob/master/HACKING.md

CONTRIBUTING.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,7 @@ We have few hard rules, but we have some:
4242
- Calls to `abort()` are forbidden in the core library. This follows from the [Writing R Extensions](https://cran.r-project.org/doc/manuals/R-exts.html) manual which states that "Under no circumstances should your compiled code ever call abort or exit".
4343
- All source code files (.h, .cpp) must be ASCII.
4444
- All C macros introduced in public headers need to be prefixed with either `SIMDJSON_` or `simdjson_`.
45+
- We avoid trailing white space characters within lines. That is, your lines of code should not terminate with unnecessary spaces. Generally, please avoid making unnecessary changes to white-space characters when contributing code.
4546

4647
Tools, tests and benchmarks are not held to these same strict rules.
4748

0 commit comments

Comments
 (0)