What problem does it solve?
FastGPT maintains two parallel CI systems—GitHub Actions for the open-source community and Forgejo Actions for the internal network—and any change to a workflow on one side must be mirrored on the other with platform-specific transformations, which is error-prone when done manually.
Core Features & Use Cases
- Dual-track workflow synchronization: Detects changes under
.github/workflows/ and applies the equivalent update to .forgejo/workflows/, keeping build and test logic functionally identical.
- Eleven conversion patterns: Covers registry address rewriting, removal of Aliyun/Docker Hub logins,
actions/* to forgejo/* action renames, permissions cleanup, intranet proxy and mirror injection, buildx driver-opts, artifact download rewrites, runner matrix defaults, workflow_dispatch version inputs, and github-script removal.
- Decision tree for new workflows: Determines whether a new GitHub workflow needs a Forgejo counterpart (build/test workflows usually do; preview/docs/helm workflows do not).
- Use Case: You add a new
build-marketplace.yml GitHub workflow that pushes images to ghcr.io. The skill rewrites it for Forgejo: dynamic registry from github.server_url, proxy variables from vars.AB_*, buildkitd config, and per-architecture artifact downloads.
Quick Start
I just modified .github/workflows/build-fastgpt.yml to add a new build argument, please sync the corresponding Forgejo workflow.