Evgeny Vereshchagin
e6175fbe45
ci: pass -Werror using CFLAGS
...
Judging by https://github.com/systemd/systemd/issues/16224 , it seems
`--werror` doesn't work with `-Db_lto=true`
2020-06-22 12:15:08 +09:00
Evgeny Vereshchagin
a2c7035976
cifuzz: build fuzz target with UBsan and MSan as well
2020-06-12 10:17:57 +02:00
Frantisek Sumsal
86a23f38ab
ci: tweak the dependency installation
2020-06-11 16:11:26 +02:00
Frantisek Sumsal
3d0a45d5da
ci: tweak the compilation options
...
Build each build with tests (slow tests and fuzzer tests as well), and
combine the LTO build with -O3.
2020-06-11 16:11:19 +02:00
Frantisek Sumsal
4e1a13db89
ci: move the build check script to workflows directory
2020-06-11 14:17:40 +02:00
Frantisek Sumsal
0664249ffc
ci: do the compiler-detection magic in the test script
...
so we have all PPA definitions at one place.
2020-06-11 14:17:37 +02:00
Frantisek Sumsal
aab86b12dd
github: move the clang/gcc build check to GH Actions
...
Travis CI is getting overloaded, so let's move some load over to GitHub
Actions.
2020-06-11 12:15:02 +02:00
Frantisek Sumsal
48c6399ad8
github: rename CIFuzz workflow file to cifuzz.yml
2020-06-11 10:22:09 +02:00
Lennart Poettering
c85b6ff1b2
docs: point contributors to list of most recent systemd releases
...
Fixes : #16083
2020-06-10 10:30:02 +02:00
Evgeny Vereshchagin
82d7a25ee6
cifuzz: protect forks from CIFuzz
...
CIFuzz isn't compatible with forks: https://github.com/google/oss-fuzz/issues/3731
2020-05-19 08:12:07 +02:00
Evgeny Vereshchagin
4b129fba30
cifuzz: set allowed-broken-targets-percentage to 0
2020-05-14 10:33:54 +02:00
Frantisek Sumsal
a114ab6373
cifuzz: fuzz the master branch on push
...
Apart from running CIFuzz for each relevant PR, let's run it
unconditionally for each push to master to detect possible issues
(caused by ignored PRs, etc.).
Followup to 94f660a8fe
.
2020-05-08 21:30:19 +03:00
Frantisek Sumsal
94f660a8fe
cifuzz: run only for relevant PRs
...
Fuzz only PRs with relevant changes (source code and fuzzer corpora) to
save resources.
2020-05-08 20:58:11 +03:00
Evgeny Vereshchagin
9494b39dac
cifuzz: upload artifacts only when the "run fuzzers" step fails
2020-05-02 11:20:30 +02:00
Frantisek Sumsal
3b4ea094e2
ci: introduce CIFuzz
...
Per-PR fuzzing provided by OSS-Fuzz using GH workflows.
See: https://google.github.io/oss-fuzz/getting-started/continuous-integration/
2020-04-24 14:06:21 +03:00
Zbigniew Jędrzejewski-Szmek
c450335bf7
github: remove direct paypal link
...
Fixes #14786 . I think it is enough if we provide the link to
SPI which sports a prominent paypal link too.
2020-02-05 21:29:34 +09:00
Lennart Poettering
90d81ee966
github: use systemd.io links in issue template
2019-12-16 09:49:51 +01:00
Zbigniew Jędrzejewski-Szmek
ab14b802b4
FUNDING: this needs to be yaml
2019-07-08 16:55:31 +02:00
Zbigniew Jędrzejewski-Szmek
3a54c53c3c
Create FUNDING.yml
2019-07-08 16:02:45 +02:00
Filipe Brandenburger
c2beadcd34
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/.
2018-09-08 13:39:03 -07:00
Filipe Brandenburger
9e825ebf4f
docs: move doc/ to docs/
...
The docs/ directory is special in GitHub, since it can be used to serve GitHub
Pages from, so there's a benefit to switching to it in order to expose it
directly as a website.
Updated references to it from the documentations themselves, from the
CONTRIBUTING.md file and from Meson build files.
2018-09-08 13:39:03 -07:00
Zbigniew Jędrzejewski-Szmek
99f0d70da9
github: use multiple issue templates
...
Github now has issue templates in the web interface, and allows
more than one to be specified. Let's split our single template
in two: bug report and RFE.
2018-05-10 07:58:38 -07:00
Lennart Poettering
f09eb7688e
doc: add a new doc/ directory, and move two markdown docs into them
...
I figure sooneror later we'll have more of these docs, hence let's give
them a clean place to be.
This leaves NEWS and README/README.md as well as the LICENSE texts in
the root directory of the project since that appears to be customary for
Free Software projects.
2018-02-27 19:59:09 +01:00
longersson
fc696d52b9
Docs: Fix spelling and capitalization ( #7408 )
2017-11-21 14:37:16 +01:00
Michael Biebl
91b8082096
CONTRIBUTING: stop mentioning "make check"
...
Since the switch to meson this information is no longer valid. HACKING already documents how to run the test suite.
See #6642
2017-08-21 09:47:07 +02:00
Lukáš Nykrýn
75d96e22d2
github: how to report bugs for older distribution versions ( #6146 )
2017-06-20 20:20:25 +02:00
Lennart Poettering
b1e98c643c
github: tweak the issue template a bit more
2017-06-19 12:15:44 +02:00
Lennart Poettering
43311625a0
github: tweak the issue template a bit, comment more
2017-06-19 12:13:28 +02:00
Mantas Mikulėnas
582c53d785
github: comment out submitter note in ISSUE_TEMPLATE
...
It's for the person filling in the form, not for people reading it later.
2017-05-22 16:07:28 +03:00
Mantas Mikulėnas
52c2abed4b
github: remove checkboxes from ISSUE_TEMPLATE
...
The issue list page thinks those are in fact todo items.
2017-05-22 16:06:50 +03:00
AsciiWolf
dc6c3de1b6
docs: use https in the mailing list url
2017-03-07 12:33:51 -03:00
Zbigniew Jędrzejewski-Szmek
c2205a0d4f
docs: add a note about reporting security vulns ( #5541 )
...
We *do* have the occasional security issue, where it would be nice to have
non-public disclosure and time to fix the issue before it's fully public. Our
github infrastracture does not make it easy to report vulnerabilities in
confidential manner, so let's leverage the distro mechanisms for that. I
think we're better off with this solution than leaving it up to individual
reporters to discover some mechanism on their own.
2017-03-07 14:33:27 +01:00
Zbigniew Jędrzejewski-Szmek
b0828828bb
CONTRIBUTING: reword the part about unsetting the label ( #4716 )
...
Only project members can do it.
2016-11-23 08:52:19 +01:00
Lennart Poettering
e4a3e122b2
documentation: add a short document describing how to test your systemd build tree ( #3763 )
2016-07-20 22:15:54 -04:00
Zbigniew Jędrzejewski-Szmek
d11343ac79
Add RELEASE.md file which lists the steps needed for release
...
I put it in .github, so it doesn't stand out too much; after all
it's not interesting to most people.
2016-06-12 22:23:57 -04:00
Zbigniew Jędrzejewski-Szmek
476ef627af
CONTRIBUTING: ask people to comment after after force-push
2016-06-12 22:21:49 -04:00
Zbigniew Jędrzejewski-Szmek
945c6e7cc0
CONTRIBUTING: remove line wrapping
...
GitHub displays this file poorly, because it preserves the newlines.
Let's try how things look without any wrapping.
2016-06-12 22:21:49 -04:00
Zbigniew Jędrzejewski-Szmek
a87c45a84b
CONTRIBUTING: recommend force-push ( #3273 )
2016-05-16 21:44:35 +02:00
daurnimator
7f4394d2fe
.github/ISSUE_TEMPLATE: Use a list for submission type so that it appears as a checkbox
2016-02-26 09:54:30 +11:00
Lennart Poettering
67b56fb29e
github: add a basic issue template
...
As documented here:
https://help.github.com/articles/creating-an-issue-template-for-your-repository/
2016-02-21 21:15:17 +01:00
Lennart Poettering
67bf157f38
github: move CONTRIBUTING.md into .github subdirectory
...
As suggested by:
https://github.com/blog/2111-issue-and-pull-request-templates
2016-02-21 21:05:02 +01:00