Migrate CI from Woodpecker to Forgejo Actions #20

Closed
opened 2026-07-07 20:58:00 +00:00 by coding-agent-marvin8 · 1 comment
coding-agent-marvin8 commented 2026-07-07 20:58:00 +00:00 (Migrated from codeberg.org)

Longwei's CI pipelines currently live in .woodpecker/. This issue tracks migrating them to Forgejo Actions (.forgejo/workflows/), following the same approach taken in zaojun.

Scope:

  • Replace all .woodpecker/*.yml files with equivalent Forgejo Actions workflows
  • All regular CI jobs to run on the zhuiri self-hosted runner
  • Weekly dependency/security checks to run on Codeberg shared runners at 02:31 AEST Saturday (cron 31 16 * * 5 UTC) — time chosen to avoid conflicts with zaojun (07), taibai (23), and feed2fedi (47)
  • Broaden WuMing AI review from 4 agents to 6: code:deepseek-v4-pro,config:deepseek-v4-flash,docs:deepseek-v4-flash,shell:deepseek-v4-flash,security:deepseek-v4-pro,tests:deepseek-v4-flash
  • Consolidate all pipelines into ci.yml + weekly-checks.yml
Longwei's CI pipelines currently live in `.woodpecker/`. This issue tracks migrating them to Forgejo Actions (`.forgejo/workflows/`), following the same approach taken in zaojun. Scope: - Replace all `.woodpecker/*.yml` files with equivalent Forgejo Actions workflows - All regular CI jobs to run on the `zhuiri` self-hosted runner - Weekly dependency/security checks to run on Codeberg shared runners at 02:31 AEST Saturday (cron `31 16 * * 5` UTC) — time chosen to avoid conflicts with zaojun (07), taibai (23), and feed2fedi (47) - Broaden WuMing AI review from 4 agents to 6: `code:deepseek-v4-pro,config:deepseek-v4-flash,docs:deepseek-v4-flash,shell:deepseek-v4-flash,security:deepseek-v4-pro,tests:deepseek-v4-flash` - Consolidate all pipelines into `ci.yml` + `weekly-checks.yml`
coding-agent-marvin8 commented 2026-07-07 21:00:17 +00:00 (Migrated from codeberg.org)

Findings:

Current .woodpecker/ files: checks.yml, weekly-checks.yml, ai-review.yml, publish-docs.yml, publish-pipy.yml.

Weekly cron conflict check — existing Forgejo Actions schedules across projects (all 16:xx UTC Friday = 02:xx AEST Saturday):

  • zaojun: 07
  • taibai: 23
  • feed2fedi: 47

Using "31 16 * * 5" for longwei (02:31 AEST Saturday).

Plan:

  1. Create .forgejo/workflows/ci.yml consolidating: pr-review (WuMing), gitleaks, checks, publish, deploy-docs — all on runs-on: zhuiri.
  2. Create .forgejo/workflows/weekly-checks.yml on runs-on: codeberg-small-lazy, cron "31 16 * * 5".
  3. Delete entire .woodpecker/ directory.
  4. WuMing agent string: code:deepseek-v4-pro,config:deepseek-v4-flash,docs:deepseek-v4-flash,shell:deepseek-v4-flash,security:deepseek-v4-pro,tests:deepseek-v4-flash (matching zaojun, adds docs and tests agents, upgrades security to pro).

Branch: feat/issue-20-forgejo-ci-migration

**Findings:** Current `.woodpecker/` files: `checks.yml`, `weekly-checks.yml`, `ai-review.yml`, `publish-docs.yml`, `publish-pipy.yml`. Weekly cron conflict check — existing Forgejo Actions schedules across projects (all `16:xx UTC Friday` = `02:xx AEST Saturday`): - zaojun: `07` - taibai: `23` - feed2fedi: `47` Using `"31 16 * * 5"` for longwei (02:31 AEST Saturday). **Plan:** 1. Create `.forgejo/workflows/ci.yml` consolidating: pr-review (WuMing), gitleaks, checks, publish, deploy-docs — all on `runs-on: zhuiri`. 2. Create `.forgejo/workflows/weekly-checks.yml` on `runs-on: codeberg-small-lazy`, cron `"31 16 * * 5"`. 3. Delete entire `.woodpecker/` directory. 4. WuMing agent string: `code:deepseek-v4-pro,config:deepseek-v4-flash,docs:deepseek-v4-flash,shell:deepseek-v4-flash,security:deepseek-v4-pro,tests:deepseek-v4-flash` (matching zaojun, adds docs and tests agents, upgrades security to pro). Branch: `feat/issue-20-forgejo-ci-migration`
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
marvin8/longwei#20
No description provided.