ci: migrate release workflow from GitHub Actions to Gitea Actions #1
Reference in New Issue
Block a user
Delete Branch "develop"
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?
Migrate the release CI workflow from GitHub Actions to Gitea Actions, and add a parallel deploy job that publishes the build to
onixbyte.cn.Changes
.github/workflows/build.ymlto.gitea/workflows/build.ymlsoftprops/action-gh-releasewithforgejo-release@v1(uses the Gitea-auto-injectedGITEA_TOKEN)onixbyte.cnfollowed by SSH extract/chown to deploy the built site to/var/httpd/dfguide(caddy:caddy)build,upload-release-asset,deploy-to-server) so the release upload and server deploy run in parallel after build.github/entirely (Dependabot config included) since the project no longer uses GitHubRequired configuration
Workflow reads from these repo-level variables and secrets in Gitea:
Variables (Settings → Actions → Variables):
DEPLOY_HOST— server hostnameDEPLOY_USER— SSH username (must be able to write the deploy path and runchown)DEPLOY_PORT— SSH portDEPLOY_PATH— deploy directorySecrets (Settings → Actions → Secrets):
DEPLOY_SSH_KEY— full SSH private key contents (multi-line, including-----BEGIN ... PRIVATE KEY-----markers).appleboy/scp-actionandappleboy/ssh-actionread the key string directly.