ci.yaml: enable-email-notifications: true

Add enable-email-notifications: true. This seems to be needed for sending information about failed runs. Apparently it doesn't make it difference if I add it to ci/workflows/.github/workflows/test-packaging.yaml.
Signed-off-by: Jan Lindemann <jan@janware.com>
standard-tests.yaml: Rename to ci.yaml
2026-06-08 14:55:04 +02:00 · 2026-06-08 14:29:30 +02:00
1 changed files with 1 additions and 1 deletions
--- a/make/project.conf
+++ b/make/project.conf
@ -36,7 +36,7 @@ build = realpath
 [pkg.requires.suse]
 run = python3
-release = rpmbuild, python3-base
+release = rpmbuild, python3-base, python3-pyright
 [pkg.requires.debian]
 run = python3
Author	SHA1	Message	Date
Jan Lindemann	9e4b216ef0	ci.yaml: enable-email-notifications: true Some checks failed CI / Packaging - Kali Linux (pull_request) Successful in 4m25s Details CI / Packaging - OpenSUSE Tumbleweed (pull_request) Failing after 2m47s Details CI / Packaging test (pull_request) Failing after 0s Details Add enable-email-notifications: true. This seems to be needed for sending information about failed runs. Apparently it doesn't make it difference if I add it to ci/workflows/.github/workflows/test-packaging.yaml. Signed-off-by: Jan Lindemann <jan@janware.com>	2026-06-08 14:55:04 +02:00
Jan Lindemann	1a56efb25a	standard-tests.yaml: Rename to ci.yaml In another attempt at making CI workflow naming more concise: - Rename standard-tests.yaml to ci.yaml Currently the contents of this file covers everything CI-related that happens in the context workflows, so for the time being, naming it ci.yaml is just fitting. And it's going to be shorter in commit message summaries. Should a real need arise, we can always split the file up again. - Shorten names again, otherwise they don't fit into Forgejo's check-mark-popup. That should be self-explanatory in context: name: Default CI -> CI jobs.CI.name: Packaging test - All supported platforms -> Packaging test Signed-off-by: Jan Lindemann <jan@janware.com>	2026-06-08 14:29:30 +02:00