feat: migrate CI to Forgejo Actions #1

Open
opened 2026-07-05 11:02:34 -07:00 by pyr0ball · 0 comments
Collaborator

Context

Focus Flow currently uses GitHub Actions (.github/workflows/). CF mirrors and
develops this repo on Forgejo. Forgejo Actions uses the same act-runner syntax as
GitHub Actions — in most cases the workflow files can be used as-is or with minor
path changes.

Work

  • Audit .github/workflows/ against Forgejo Actions compatibility
  • Add .forgejo/workflows/ equivalents
  • Verify Earthly build target runs correctly on CF's Gitea runner
  • Keep .github/workflows/ intact for upstream compatibility

Why

CF's CI infrastructure runs on Forgejo. Having Actions green here means CF
contributors get feedback on PRs without depending on GitHub.

## Context Focus Flow currently uses GitHub Actions (`.github/workflows/`). CF mirrors and develops this repo on Forgejo. Forgejo Actions uses the same act-runner syntax as GitHub Actions — in most cases the workflow files can be used as-is or with minor path changes. ## Work - Audit `.github/workflows/` against Forgejo Actions compatibility - Add `.forgejo/workflows/` equivalents - Verify Earthly build target runs correctly on CF's Gitea runner - Keep `.github/workflows/` intact for upstream compatibility ## Why CF's CI infrastructure runs on Forgejo. Having Actions green here means CF contributors get feedback on PRs without depending on GitHub.
pyr0ball added this to the CF Integration Layer milestone 2026-07-05 19:56:20 -07:00
pyr0ball added the
area:cf-integration
label 2026-07-05 19:56:20 -07:00
Sign in to join this conversation.
No project
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: eva/focus-flow#1
No description provided.