diff options
| author | Lennart Poettering <lennart@poettering.net> | 2018-06-07 16:26:00 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2018-06-07 16:26:00 +0200 |
| commit | ecb462dbf5f01a92dbf2385d6a0d1ed4de944014 (patch) | |
| tree | f1aae3d4d6a99712ab595f4b9f9702db3ef6deef | |
| parent | 7c2c028c8538f6b59a37c583f744e3905da7e67f (diff) | |
| download | systemd-ecb462dbf5f01a92dbf2385d6a0d1ed4de944014.tar.gz | |
HACKING: link up CODE_QUALITY.md
| -rw-r--r-- | doc/HACKING | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/HACKING b/doc/HACKING index 92001be94e..182b0bac8c 100644 --- a/doc/HACKING +++ b/doc/HACKING @@ -20,6 +20,11 @@ test executable. For features at a higher level, tests in src/test/ are very strongly recommended. If that is no possible, integration tests in test/ are encouraged. +Please also have a look at our list of code quality tools we have setup for systemd, +to ensure our codebase stays in good shape: + + https://github.com/systemd/systemd/blob/master/doc/CODE_QUALITY.md + Please always test your work before submitting a PR. For many of the components of systemd testing is straight-forward as you can simply compile systemd and run the relevant tool from the build directory. |