summaryrefslogtreecommitdiff
path: root/docs/HACKING
diff options
context:
space:
mode:
authorFilipe Brandenburger <filbranden@google.com>2018-09-07 01:07:06 -0700
committerFilipe Brandenburger <filbranden@google.com>2018-09-08 13:39:03 -0700
commitc2beadcd34d2b1da1a16330377d484dedfbc8a32 (patch)
tree2df4d753212d05e6459da06cdc1c78246754f4e9 /docs/HACKING
parent9e825ebf4f5029ae6cb072ac568d7838e0762a9e (diff)
downloadsystemd-c2beadcd34d2b1da1a16330377d484dedfbc8a32.tar.gz
systemd-c2beadcd34d2b1da1a16330377d484dedfbc8a32.tar.bz2
systemd-c2beadcd34d2b1da1a16330377d484dedfbc8a32.zip
docs: move markdown docs from .github/ to docs/
The GitHub guide on contributing file says: "Decide whether to store your contributing guidelines in your repository's root, docs, or .github directory." https://help.github.com/articles/setting-guidelines-for-repository-contributors/#adding-a-contributing-file But there's really no advantage to keeping it in the hidden .github/, since these are public and really belong together with the other documentation. We can still keep the issue templates under .github/, since they are not really documentation on their own. Updated the links pointing to CONTRIBUTING.md to refer to the one in docs/.
Diffstat (limited to 'docs/HACKING')
-rw-r--r--docs/HACKING2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/HACKING b/docs/HACKING
index c7b700e6a7..1778e4822d 100644
--- a/docs/HACKING
+++ b/docs/HACKING
@@ -9,7 +9,7 @@ Request (PR):
Please make sure to follow our Coding Style when submitting patches. See
docs/CODING_STYLE for details. Also have a look at our Contribution Guidelines:
- https://github.com/systemd/systemd/blob/master/.github/CONTRIBUTING.md
+ https://github.com/systemd/systemd/blob/master/docs/CONTRIBUTING.md
When adding new functionality, tests should be added. For shared functionality
(in src/basic and src/shared) unit tests should be sufficient. The general