summaryrefslogtreecommitdiff
path: root/.github
Commit message (Collapse)AuthorAgeFilesLines
* ci: introduce a watchdog for the sanitized unit test runFrantisek Sumsal2021-01-131-0/+10
|
* ci: optimize the sanitized build under gcc as wellFrantisek Sumsal2021-01-131-1/+3
|
* ci: drop the `unbuffer` workaroundFrantisek Sumsal2021-01-121-6/+1
| | | | It actually didn't do anything, the issue was somewhere else.
* ci: move the Coverity job to GitHub ActionsFrantisek Sumsal2021-01-111-0/+39
|
* ci: drop a forgotten empty lineFrantisek Sumsal2021-01-111-1/+0
|
* ci: do not build with --optimization=1 with ClangLuca Boccassi2021-01-101-2/+1
|
* ci: move Travis CI unit test jobs to GH ActionsFrantisek Sumsal2021-01-082-0/+103
|
* Move shared mkosi settings to a single file in mkosi.default.d/Daan De Meyer2021-01-061-3/+6
|
* CI: Update to mkosi github action to v9Daan De Meyer2021-01-011-5/+2
|
* github: add the missing tpm2 optional dependencyFrantisek Sumsal2020-12-201-0/+1
|
* Add more matching rules to GA labeler bot for subcomponentsLuca Boccassi2020-12-191-0/+12
|
* False positives in GA labeler botLuca Boccassi2020-12-191-2/+0
| | | | | Don't automatically match on man/* and **/meson.build, since we change those files as part of larger changes that we usually don't mark that way
* Add Pull Request LabelerJameer Pathan2020-12-142-0/+41
|
* CI: Add mkosi boot testsDaan De Meyer2020-12-042-0/+69
| | | | | | Using the new mkosi Github Action, we can add some simple boot tests for the systemd mkosi configs. This makes sure these keep working as expected.
* ci: also set -Dfuzz-tests=true if -Dslow-tests=trueYu Watanabe2020-11-131-1/+1
|
* ci: add the libfido2 dependency for better coverageFrantisek Sumsal2020-10-211-1/+2
|
* ci: build with clang-11 as wellFrantisek Sumsal2020-10-211-0/+1
| | | | | The LLVM nightly repositories now have a separate branch for clang-11, so let's build with it as well.
* ci: bump the 'build test' image to Ubuntu FocalFrantisek Sumsal2020-10-212-2/+2
|
* github: ask for arch+kernel in bug report formLennart Poettering2020-10-021-1/+8
| | | | | | | Quite often we see kernel and arch specific issues, let's ask for the version right-away when people file the issue. Other tweaks.
* Revert "ci: turn off the "upstream-systemd-ci" ppa"Evgeny Vereshchagin2020-07-151-1/+1
| | | | This reverts commit d4ff79bbe1f33fb17e7add3bd520c08f405a79b1.
* ci: turn off the "upstream-systemd-ci" ppaEvgeny Vereshchagin2020-07-141-1/+1
| | | | | | | | | | | | | Judging by https://launchpad.net/~upstream-systemd-ci/+archive/ubuntu/systemd-ci/+packages, it got updated about 15 hours ago and the "build check" action has been failing with ``` The following packages have unmet dependencies: kbd : Depends: console-setup but it is not going to be installed or E: Unable to correct problems, you have held broken packages. console-setup-mini but it is not going to be installed ``` since then
* ci: pass -Werror using CFLAGSEvgeny Vereshchagin2020-06-221-1/+1
| | | | | Judging by https://github.com/systemd/systemd/issues/16224, it seems `--werror` doesn't work with `-Db_lto=true`
* cifuzz: build fuzz target with UBsan and MSan as wellEvgeny Vereshchagin2020-06-121-3/+9
|
* ci: tweak the dependency installationFrantisek Sumsal2020-06-111-7/+10
|
* ci: tweak the compilation optionsFrantisek Sumsal2020-06-111-3/+3
| | | | | Build each build with tests (slow tests and fuzzer tests as well), and combine the LTO build with -O3.
* ci: move the build check script to workflows directoryFrantisek Sumsal2020-06-112-3/+116
|
* ci: do the compiler-detection magic in the test scriptFrantisek Sumsal2020-06-111-18/+3
| | | | so we have all PPA definitions at one place.
* github: move the clang/gcc build check to GH ActionsFrantisek Sumsal2020-06-111-0/+44
| | | | | Travis CI is getting overloaded, so let's move some load over to GitHub Actions.
* github: rename CIFuzz workflow file to cifuzz.ymlFrantisek Sumsal2020-06-111-0/+0
|
* docs: point contributors to list of most recent systemd releasesLennart Poettering2020-06-101-1/+2
| | | | Fixes: #16083
* cifuzz: protect forks from CIFuzzEvgeny Vereshchagin2020-05-191-0/+1
| | | | CIFuzz isn't compatible with forks: https://github.com/google/oss-fuzz/issues/3731
* cifuzz: set allowed-broken-targets-percentage to 0Evgeny Vereshchagin2020-05-141-0/+1
|
* cifuzz: fuzz the master branch on pushFrantisek Sumsal2020-05-081-0/+3
| | | | | | | | 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 94f660a8fe6144b9153c8acaf9e6bb9e47e14b97.
* cifuzz: run only for relevant PRsFrantisek Sumsal2020-05-081-1/+9
| | | | | Fuzz only PRs with relevant changes (source code and fuzzer corpora) to save resources.
* cifuzz: upload artifacts only when the "run fuzzers" step failsEvgeny Vereshchagin2020-05-021-1/+2
|
* ci: introduce CIFuzzFrantisek Sumsal2020-04-241-0/+27
| | | | | | Per-PR fuzzing provided by OSS-Fuzz using GH workflows. See: https://google.github.io/oss-fuzz/getting-started/continuous-integration/
* github: remove direct paypal linkZbigniew Jędrzejewski-Szmek2020-02-051-1/+1
| | | | | Fixes #14786. I think it is enough if we provide the link to SPI which sports a prominent paypal link too.
* github: use systemd.io links in issue templateLennart Poettering2019-12-161-1/+1
|
* FUNDING: this needs to be yamlZbigniew Jędrzejewski-Szmek2019-07-081-1/+1
|
* Create FUNDING.ymlZbigniew Jędrzejewski-Szmek2019-07-081-0/+1
|
* docs: move markdown docs from .github/ to docs/Filipe Brandenburger2018-09-083-50/+1
| | | | | | | | | | | | | | | 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/.
* docs: move doc/ to docs/Filipe Brandenburger2018-09-081-2/+2
| | | | | | | | | 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.
* github: use multiple issue templatesZbigniew Jędrzejewski-Szmek2018-05-103-31/+36
| | | | | | 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.
* doc: add a new doc/ directory, and move two markdown docs into themLennart Poettering2018-02-271-2/+2
| | | | | | | | | 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.
* Docs: Fix spelling and capitalization (#7408)longersson2017-11-211-1/+1
|
* CONTRIBUTING: stop mentioning "make check"Michael Biebl2017-08-211-1/+1
| | | | | Since the switch to meson this information is no longer valid. HACKING already documents how to run the test suite. See #6642
* github: how to report bugs for older distribution versions (#6146)Lukáš Nykrýn2017-06-202-0/+7
|
* github: tweak the issue template a bit moreLennart Poettering2017-06-191-1/+1
|
* github: tweak the issue template a bit, comment moreLennart Poettering2017-06-191-2/+2
|
* github: comment out submitter note in ISSUE_TEMPLATEMantas Mikulėnas2017-05-221-1/+1
| | | | It's for the person filling in the form, not for people reading it later.
View Lorry Controller Status