Migrate Loopbound CI to Forgejo Actions #3
Loading…
Reference in a new issue
No description provided.
Delete branch "mcp/forgejo-ci-migration"
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?
Summary
Migrates Loopbound's CI contract from historical GitHub Actions to Forgejo Actions without changing gameplay, content, persistence, dependencies, package versions, runtime behavior, or active Slice work.
Base
main:7e24529b2a9e419218d2a1423d832b1bf587c8efCurrent PR HEAD:
a45bfc337e4f47efca72a4f70ca103a26cae84b4Changes
.forgejo/workflows/pull-request.ymlas the authoritative core Forgejo PR workflow;.forgejo/workflows/platform.ymlas the conditional Tauri/Rust platform workflow;Desktop / Tauri cargo checkwhen Tauri/platform paths change;linux-amd64runner label;npm auditas a failing security gate;npm run format:checkto cover Forgejo workflow YAML;CI_CHECKS.mdaround Forgejo Actions, exact-HEAD acceptance, conditional platform validation and manual dispatch;.github/workflows/ci.ymland.github/workflows/platform.ymlso they cannot be mistaken for current CI authority.The historical GitHub workflow files remain only because the current MCP repository-file API does not expose a safe delete operation. They are manual-only migration notices and no longer implement CI.
Required Forgejo checks
Always-required core gate:
Conditional platform gate for Tauri/platform changes:
Infrastructure blocker
Forgejo currently reports
has_actions: falseforalexander/Loopbound.This PR therefore does not claim green Forgejo CI. Both Forgejo workflow files are present and discoverable on the exact PR HEAD, but workflow execution is disabled at repository level.
The currently exposed prox2-mcp-gateway toolset does not provide the Forgejo repository-setting mutation needed to enable Actions, so the setting cannot be safely changed through the required repository connection from this task.
The Forgejo instance itself has working Actions in other repositories using the
linux-amd64runner label, so the migration targets that proven runner contract.After repository Actions is enabled, retrigger this PR and accept only Forgejo runs whose commit SHA exactly equals the then-current PR HEAD.
Scope protection
No changes were made to Forgejo PR #1, Forgejo PR #2,
planning/slice-6-readiness,feature/slice-5-applied-skill-learning, or their SHA-identical migration branches.Merge
Do not merge automatically. Manual review/merge by the repository owner is expected.
Implementation update — repository-side CI migration is now complete on exact PR HEAD
a45bfc337e4f47efca72a4f70ca103a26cae84b4.Additional reconciliation completed:
.forgejo/workflows/platform.yml;linux-amd64runner contract and pinned Forgejo-hosted checkout/artifact actions;Forgejo still reports
has_actions: falsefor this repository. The currently exposed prox2-mcp-gateway toolset has no repository-settings mutation for enabling Actions, so no exact-HEAD run can exist yet. This is now the only proven blocker to executing the new workflows; it is not being treated as a pass.Do not merge based on historical GitHub status. After Actions is enabled, run/retrigger the Forgejo workflows on this exact PR HEAD and accept only the resulting Forgejo statuses.