chore(ci): move CI to Forgejo Actions #9
No reviewers
Labels
No labels
Agent
Ignore
Agent
In Progress
Agent
Planned
Agent
Planning
Agent
Ready
Agent
Triage
Compat
Breaking
Kind
Bug
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Security
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
lucas/nanoKontroller2!9
Loading…
Reference in a new issue
No description provided.
Delete branch "agent/issue-7-forgejo-ci"
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?
Replaces the GitHub-only pipeline with a single Forgejo workflow at
.forgejo/workflows/build.ymland removes.github/entirely (workflow, funding file, issue templates — no Forgejo replacements, as requested).The workflow runs on the stock
dockerlabel, installs WirePlumber, RtMidi, cxxopts and concurrentqueue from trixie's apt packages, pulls CMake 4.2 viaget-cmake(trixie ships 3.31), builds glaze and magic_enum from pinned tags, then configures and builds. No artifacts, packaging or release publishing.Verification is the run itself; marking ready once the checks on this head are green.
Closes: #7
Blocker on verification, not on the change itself.
No workflow run was created for the pushed head
bff0475:forgejo_read_commit_statusreports no status checks several minutes after the push, the repository's/actionspage returns 404, and the repository API reports"has_actions": false.That is the contingency the plan anticipated: the Actions unit is disabled for
lucas/nanoKontroller2, so no runner can ever pick this workflow up. Enabling it is a repository-administration matter outside this change, and the plan says to report it rather than rework the workflow — so the workflow is left exactly as planned.Once Actions is enabled, a push (or a re-run) on this branch should produce the
Buildcheck; I can then confirm the apt dependency set, the configure step and the build from the job log.The deletions did land:
.github/(workflow,FUNDING.yml, both issue templates) no longer exists on this branch.WIP: chore(ci): move CI to Forgejo Actionsto chore(ci): move CI to Forgejo Actions