projects / thirdparty / systemd.git / blame
| Commit | Line | Data |
|---|---|---|
| cc5fddef LP |
1 | # Contributing |
| 2 | ||
| 3 | We welcome contributions from everyone. However, please follow the following guidelines when posting a GitHub Pull | |
| 4 | Request or filing a GitHub Issue on the systemd project: | |
| 5 | ||
| 6 | ## Filing Issues | |
| 7 | ||
| 8 | * We use GitHub Issues **exclusively** for tracking **bugs** and **feature** **requests** of systemd. If you are | |
| 9 | looking for help, please contact our [mailing list](http://lists.freedesktop.org/mailman/listinfo/systemd-devel) | |
| 10 | instead. | |
| 11 | * We only track bugs in the **two** **most** **recently** **released** **versions** of systemd in the GitHub Issue | |
| 12 | tracker. If you are using an older version of systemd, please contact your distribution's bug tracker instead. | |
| 13 | * When filing an issue, specify the **systemd** **version** you are experiencing the issue with. Also, indicate which | |
| 14 | **distribution** you are using. | |
| 15 | * Please include an explanation how to reproduce the issue you are pointing out. | |
| 16 | ||
| 17 | Following these guidelines makes it easier for us to process your issue, and ensures we won't close your issue | |
| 18 | right-away for being misfiled. | |
| 19 | ||
| 20 | ## Posting Pull Requests | |
| 21 | ||
| 22 | * Make sure to post PRs only relative to a very recent git master. | |
| 23 | * Follow our [Coding Style](https://raw.githubusercontent.com/systemd/systemd/master/CODING_STYLE) when contributing | |
| 24 | code. This is a requirement for all code we merge. | |
| 25 | * Make sure to run "make check" locally, before posting your PR. We use a CI system, meaning we don't even look at your | |
| 26 | PR, if the build and tests don't pass. | |
| 5362df0e | 27 | * If you need to update the code in an existing PR, please consider opening a new PR (mentioning in it which old PR it |
| cc5fddef LP |
28 | replaces) and closing the old PR. This is much preferable over force-pushing a new patch set into the PR's branch, as |
| 29 | commit comments aren't lost that way. That said, we don't follow this rule ourselves quite often, hence this is | |
| 30 | really just a say as we say, not say as we do... | |
| 31 | ||
| 32 | ## Final Words | |
| 33 | ||
| 34 | We'd like to apologize in advance if we are not able to process and reply to your issue or PR right-away. We have a lot | |
| 35 | of work to do, but we are trying our best! | |
| 36 | ||
| 37 | Thank you very much for your contributions! |