Move CI workflows to .forgejo/workflows #16

Merged

linus merged 1 commit from jerry/move-workflows-to-forgejo-develop into develop

2026-10-18 02:20:06 +00:00

jerry commented

2026-10-18 02:05:52 +00:00

Contributor

Forgejo reads .forgejo/workflows and ignores .gitea/workflows, so since the move from Gitea CI on this repo wouldn't run. This moves release-tag.yaml, test-pr.yaml over.

Edits: gitea.* contexts become github.*, and artifact actions are pinned to the code.forgejo.org v4 versions where they were used (upstream v4 refuses to run on non-GitHub servers).

Forgejo reads .forgejo/workflows and ignores .gitea/workflows, so since the move from Gitea CI on this repo wouldn't run. This moves release-tag.yaml, test-pr.yaml over. Edits: gitea.* contexts become github.*, and artifact actions are pinned to the code.forgejo.org v4 versions where they were used (upstream v4 refuses to run on non-GitHub servers).

jerry added 1 commit

2026-10-18 02:05:52 +00:00

Move CI workflows to .forgejo/workflows

CI / check-and-test (pull_request) Successful in 50s

Details

22ac6bed2f

The server moved from Gitea to Forgejo, which reads .forgejo/workflows and ignores .gitea/workflows, so CI would silently stop running here. Move the files over. While at it, swap the gitea.* expression contexts for github.* (Forgejo rejects gitea.*) and point upload/download-artifact@v4 at code.forgejo.org/forgejo, since upstream v4 refuses to run on non-GitHub servers.