Skip to content

Commit fc2e120

Browse files
authoredOct 13, 2020
Document how to work with ClangFormat (#10468)
To avoid the common misunderstanding where a contributor thinks they must apply the unsuitable formatting requests ClangFormat makes.
1 parent 7499ebe commit fc2e120

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed
 

‎.github/CONTRIBUTING.md

+8
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,14 @@ Contributions are welcome! Here's how you can help:
4343
4. The code's interfaces are well designed, regardless of other aspects that might need more work in the future.
4444
5. It uses protocols and formats which include the required compatibility.
4545

46+
### Important note about automated GitHub checks
47+
48+
When you submit a pull request, GitHub automatically runs checks on the Minetest Engine combined with your changes. One of these checks is called 'cpp lint / clang format', which checks code formatting.
49+
Because formatting for readability requires human judgement this check often fails and often makes unsuitable formatting requests which make code readability worse.
50+
51+
If this check fails, look at the details to check for any clear mistakes and correct those. However you should not apply everything ClangFormat requests, ignore requests that make code readability worse and any other clearly unsuitable requests.
52+
Discuss with a core developer if in any doubt and for how to progress.
53+
4654
## Issues
4755

4856
If you experience an issue, we would like to know the details - especially when a stable release is on the way.

0 commit comments

Comments
 (0)
Please sign in to comment.