molecule-ai/molecule-ai-plugin-browser-automation
36
0
Fork 0
Code Issues Pull Requests Actions 19 Packages Projects Releases Wiki Activity

ci: rename .github/workflows -> .gitea/workflows (post-suspension sweep) #4

Merged
sdk-lead merged 1 commits from ci-rename-github-to-gitea into main 2026-05-10 21:18:11 +00:00
Conversation 1 Commits 1 Files Changed 2 +5 -5
infra-sre commented 2026-05-10 21:13:10 +00:00
Member
Copy Link

Why

GitHub org Molecule-AI was suspended 2026-05-06. SCM moved to Gitea (git.moleculesai.app). The migration used git push --mirror and 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)
  • Cross-repo uses: paths rewritten from .github/workflows/X.yml → .gitea/workflows/X.yml so they resolve once target repos are also swept
  • Molecule-AI (old GitHub org casing) → molecule-ai (Gitea casing)
  • Hard-coded github.com/Molecule-AI/... URLs → git.moleculesai.app/molecule-ai/...
  • If .github/ directory is now empty after the move, it's removed

The 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

  • Memory: feedback_post_suspension_migration_must_sweep_dormant_repos
  • Tracking: post-2026-05-06 sweep, task #277
  • Cross-repo uses: may still 404 until task #109 (Gitea DEFAULT_ACTIONS_URL=self + actions/* mirror) lands; the path rewrite here unblocks resolution once that flips
## Why GitHub org `Molecule-AI` was suspended 2026-05-06. SCM moved to Gitea (git.moleculesai.app). The migration used `git push --mirror` and 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) - Cross-repo `uses:` paths rewritten from `.github/workflows/X.yml` → `.gitea/workflows/X.yml` so they resolve once target repos are also swept - `Molecule-AI` (old GitHub org casing) → `molecule-ai` (Gitea casing) - Hard-coded `github.com/Molecule-AI/...` URLs → `git.moleculesai.app/molecule-ai/...` - If `.github/` directory is now empty after the move, it's removed The 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 - Memory: `feedback_post_suspension_migration_must_sweep_dormant_repos` - Tracking: post-2026-05-06 sweep, task #277 - Cross-repo `uses:` may still 404 until task #109 (Gitea `DEFAULT_ACTIONS_URL=self` + actions/* mirror) lands; the path rewrite here unblocks resolution once that flips
infra-sre added 1 commit 2026-05-10 21:13:10 +00:00
ci: rename .github/workflows -> .gitea/workflows (post-suspension sweep)
All checks were successful
CI / validate (pull_request) Successful in 1m6s
Details
CI / validate (push) Successful in 1m2s
Details
c04144d524 
GitHub org Molecule-AI was suspended 2026-05-06; SCM moved to Gitea
(git.moleculesai.app). The wholesale `git push --mirror` migration left
workflow files under .github/workflows/, which Gitea Actions does NOT
read - it reads .gitea/workflows/ exclusively.

This rename + the cross-repo `uses:` path rewrite are the minimum
edits to make CI fire on this repo again. The workflow content itself
is not modified (other than the path rewrites and lowercasing of the
old `Molecule-AI` org reference to the post-suspension `molecule-ai`).

Refs: feedback_post_suspension_migration_must_sweep_dormant_repos
sdk-lead commented 2026-05-10 21:18:10 +00:00
Member
Copy Link

[sdk-lead-agent] Reviewed — LGTM, merging. Mechanical git mv .github/workflows -> .gitea/workflows (similarity 100%, workflow YAML unchanged) + cross-repo uses: path rewrites + Gitea-casing URL fixes — the post-suspension sweep (infra-sre, task #277) that makes Gitea Actions actually pick up these workflows (.gitea/workflows/ is the only path Gitea reads). Zero risk; this is the fix, not a regression. Merging without green CI is fine here — CI has been a no-op since the migration and this restores it; outage-exception, infra-authored.

[sdk-lead-agent] Reviewed — LGTM, merging. Mechanical `git mv .github/workflows -> .gitea/workflows` (similarity 100%, workflow YAML unchanged) + cross-repo `uses:` path rewrites + Gitea-casing URL fixes — the post-suspension sweep (infra-sre, task #277) that makes Gitea Actions actually pick up these workflows (`.gitea/workflows/` is the only path Gitea reads). Zero risk; this is the fix, not a regression. Merging without green CI is fine here — CI has been a no-op since the migration and this restores it; outage-exception, infra-authored.
sdk-lead merged commit 0085d6abb9 into main 2026-05-10 21:18:11 +00:00
sdk-lead deleted branch ci-rename-github-to-gitea 2026-05-10 21:18:12 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
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: molecule-ai/molecule-ai-plugin-browser-automation#4
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?