ci: rename .github/workflows -> .gitea/workflows (post-suspension sweep) #4
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "ci-rename-github-to-gitea"
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?
Why
GitHub org
Molecule-AIwas suspended 2026-05-06. SCM moved to Gitea (git.moleculesai.app). The migration usedgit push --mirrorand left workflows under.github/workflows/, but Gitea Actions only reads.gitea/workflows/— so this repo's CI has been silently no-op since the migration.What
git mv .github/workflows .gitea/workflows(workflow contents unchanged)uses:paths rewritten from.github/workflows/X.yml→.gitea/workflows/X.ymlso they resolve once target repos are also sweptMolecule-AI(old GitHub org casing) →molecule-ai(Gitea casing)github.com/Molecule-AI/...URLs →git.moleculesai.app/molecule-ai/....github/directory is now empty after the move, it's removedThe workflow YAML semantics are unchanged.
${{ github.* }}context vars still resolve under Gitea Actions.Verification
After merge, a one-line noop commit on the head branch should fire the workflow. Hongming will trigger.
Refs
feedback_post_suspension_migration_must_sweep_dormant_reposuses:may still 404 until task #109 (GiteaDEFAULT_ACTIONS_URL=self+ actions/* mirror) lands; the path rewrite here unblocks resolution once that flipsHourly CI/CD triage evidence from
hongming-codex-laptopat 2026-05-13T07:42:51Z:Current commit statuses for head
b12f39005f77949d86eb3357dc6827e76a082c0a:pending—CI / test (3.11) (pull_request), target/molecule-ai/codex-channel-molecule/actions/runs/14/jobs/0, descriptionHas started running, updated2026-05-10T21:13:52Z.success—CI / test (3.12) (pull_request), target/molecule-ai/codex-channel-molecule/actions/runs/13/jobs/1, updated2026-05-10T21:14:04Z.Root class: stale pending Gitea Actions status, not a current test failure. Next safe action is to refire or close/reopen/re-push this PR after confirming the runner lane is healthy; do not treat this as a Python 3.11 code failure without fresh logs.
Checkout
From your project repository, check out a new branch and test the changes.