diff options
| author | Lennart Poettering <lennart@poettering.net> | 2016-07-21 04:15:54 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2016-07-20 22:15:54 -0400 |
| commit | e4a3e122b2e820ba33cc858d3c8b1389f1c8f745 (patch) | |
| tree | a1a1580f442fc9471fbcb7c43f1f85a7d37918a1 /.github | |
| parent | 176e51b7102d7bba875e58b85b59e2ed7e30bc89 (diff) | |
documentation: add a short document describing how to test your systemd build tree (#3763)
Diffstat (limited to '.github')
| -rw-r--r-- | .github/CONTRIBUTING.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 4857e94733..8a6db1f629 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -15,6 +15,7 @@ Following these guidelines makes it easier for us to process your issue, and ens * Make sure to post PRs only relative to a very recent git master. * Follow our [Coding Style](https://raw.githubusercontent.com/systemd/systemd/master/CODING_STYLE) when contributing code. This is a requirement for all code we merge. +* Please make sure to test your change before submitting the PR. See [HACKING](https://raw.githubusercontent.com/systemd/systemd/master/HACKING) for details how to do this. * Make sure to run "make check" locally, before posting your PR. We use a CI system, meaning we don't even look at your PR, if the build and tests don't pass. * If you need to update the code in an existing PR, force-push into the same branch, overriding old commits with new versions. * After you have pushed a new version, try to remove the `reviewed/needs-rework` label. Also add a comment about the new version (no notification is sent just for the commits, so it's easy to miss the update without an explicit comment). |