Move CI workflows to .forgejo/workflows #24

Merged

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

2026-10-18 02:15:12 +00:00

jerry commented

2026-10-18 02:04: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 ci.yaml, fmt.yaml, release.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).

The ash feature branch already got this move; this PR is for the long-lived branch only.

Forgejo reads .forgejo/workflows and ignores .gitea/workflows, so since the move from Gitea CI on this repo wouldn't run. This moves ci.yaml, fmt.yaml, release.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). The ash feature branch already got this move; this PR is for the long-lived branch only.

jerry added 1 commit

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

Move CI workflows to .forgejo/workflows

Format / gofmt (pull_request) Successful in 30s

Details

CI / Go Tests (pull_request) Successful in 1m59s

Details

CI / Build (pull_request) Successful in 1m9s

Details

58fb2cf69c

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.