Migrate CI from GitHub Actions to Forgejo Actions #2
Labels
No labels
area/ai
area/backend
area/frontend
area/infra
area/scheduler
area/wled
good-first-issue
priority/high
priority/low
priority/medium
type/bug
type/chore
type/ci-cd
type/docs
type/feature
type/qa
v1.0.0
v1.1.0
v1.2.0
v2.0.0
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
rbrooks/Iris-WLED#2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Move the existing CI pipeline off GitHub Actions and onto Forgejo Actions so that CI runs on our own infrastructure (git.rhoving.com).
Scope
.github/workflows/ci.ymlto.forgejo/workflows/ci.yml, preserving all existing jobs:ubuntu-latestvsdockervs custom) and setruns-onaccordingly..github/workflows/ci.ymlonce the Forgejo pipeline is green.Notes
Forgejo Actions is largely GitHub-Actions-compatible, so most step definitions carry over unchanged. Action resolution (
actions/checkout@v4, etc.) depends on the runner's configured action registry.Acceptance criteria
maintrigger the Forgejo pipeline.github/workflows/ci.ymldeletedRelated: test-coverage expansion tracked separately.