Migrate CI from Woodpecker to Forgejo Actions #20
Labels
No labels
bug
contribution welcome
duplicate
enhancement
good first issue
help wanted
invalid
question
upstream
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Reference
marvin8/longwei#20
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
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:
.woodpecker/*.ymlfiles with equivalent Forgejo Actions workflowszhuiriself-hosted runner31 16 * * 5UTC) — time chosen to avoid conflicts with zaojun (07), taibai (23), and feed2fedi (47)code:deepseek-v4-pro,config:deepseek-v4-flash,docs:deepseek-v4-flash,shell:deepseek-v4-flash,security:deepseek-v4-pro,tests:deepseek-v4-flashci.yml+weekly-checks.ymlFindings:
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):072347Using
"31 16 * * 5"for longwei (02:31 AEST Saturday).Plan:
.forgejo/workflows/ci.ymlconsolidating: pr-review (WuMing), gitleaks, checks, publish, deploy-docs — all onruns-on: zhuiri..forgejo/workflows/weekly-checks.ymlonruns-on: codeberg-small-lazy, cron"31 16 * * 5"..woodpecker/directory.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