diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2016-05-31 13:32:23 -0400 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2016-06-12 22:21:49 -0400 |
| commit | 476ef627afd01ac97080280ccdf6489101b0f1bc (patch) | |
| tree | ee499fd945cf513f32140209ee855ad407c4ab3c | |
| parent | 945c6e7cc06b3c6ffc13fe3c76d98f17dce500d1 (diff) | |
CONTRIBUTING: ask people to comment after after force-push
| -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 18ae1d0aec..4857e94733 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -17,6 +17,7 @@ Following these guidelines makes it easier for us to process your issue, and ens * 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. * 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). ## Final Words |