janware/jw-pkg
1
Code Pull requests Activity Actions

ci.yaml: Replace standard-tests.yaml by ci.yaml #2

Merged
Jan Lindemann merged 2 commits from jan/feature/20260608-ci-yaml-streamline-workflow into master 2026-06-08 19:32:27 +02:00 AGit
Conversation 0 Commits 2 Files changed 1 +4 -3
Jan Lindemann commented 2026-06-08 15:00:28 +02:00
Owner
Copy link

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

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.

#### 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 #### 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.
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>
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
9e4b216ef0
 
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>
Jan Lindemann scheduled this pull request to auto merge when all checks succeed 2026-06-08 15:00:29 +02:00
Jan Lindemann force-pushed jan/feature/20260608-ci-yaml-streamline-workflow from 9e4b216ef0
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
to 00af6a2b37
All checks were successful
CI / Packaging - Kali Linux (pull_request) Successful in 3m21s
Details
CI / Packaging - OpenSUSE Tumbleweed (pull_request) Successful in 3m22s
Details
CI / Packaging test (pull_request) Successful in 0s
Details
CI / Packaging - Kali Linux (push) Successful in 3m17s
Details
CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 3m15s
Details
CI / Packaging test (push) Successful in 0s
Details
2026-06-08 19:32:26 +02:00 Compare
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
janware/jw-pkg!2
No description provided.