| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
345364cd85
|
ci.yaml: test-packaging.yaml@{master-test -> master}
All checks were successful
CI / Packaging - Kali Linux (pull_request) Successful in 3m16s
CI / Packaging - OpenSUSE Tumbleweed (pull_request) Successful in 3m12s
CI / Packaging test (pull_request) Successful in 0s
CI / Packaging - Kali Linux (push) Successful in 3m21s
CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 3m12s
CI / Packaging test (push) Successful in 0s
Don't use master-test branch from ci/workflows for test-packaging.yaml, because it might mo away. Use master instead. Signed-off-by: Jan Lindemann <jan@janware.com> |
|||
|
00af6a2b37
|
ci.yaml: enable-email-notifications: true
All checks were successful
CI / Packaging - Kali Linux (pull_request) Successful in 3m21s
CI / Packaging - OpenSUSE Tumbleweed (pull_request) Successful in 3m22s
CI / Packaging test (pull_request) Successful in 0s
CI / Packaging - Kali Linux (push) Successful in 3m17s
CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 3m15s
CI / Packaging test (push) Successful in 0s
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> |
|||
|
ace0e915ec
|
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> |