tianma-if
ee49d280ec
Read-only Cloudflare forks were getting silent green no-ops when already aligned, or unclear merge skips after Sync fork. Align deploy-only forks with reset, keep merge for customized trees, always write a job summary, and document force_redeploy plus an optional Cloudflare Deploy Hook.
2.0 KiB
2.0 KiB
Cloudflare Workers Builds
Setup
Use the build and deploy commands from the online deployment guide, with root directory / and production branch main.
Authorization:
- Approve the Cloudflare Workers & Pages GitHub App for the deployment repository.
- If the Agent integration needs a Cloudflare API token, use a User API Token limited to the target account.
- Configure the deployment API token in Cloudflare under Worker -> Settings -> Builds -> API token.
Updates and troubleshooting
- A push to
mainbuilds, applies D1 migrations, deploys, and verifies EdgeEver. - Update deployed EdgeEver keeps a deployment Fork as an upstream deploy mirror:
- Default channel
stabletracks the latest formal Release tag. - Set the GitHub Repository Variable
EDGE_EVER_UPDATE_CHANNEL=edgeto follow upstreammain. - Read-only forks (no app code changes) reset onto the target when behind; customized forks merge and fail closed on conflicts.
- Every run writes a job Summary with channel, target version, decision reason, and whether a push happened. A green run that says Already on upstream target is success, not a silent failure.
- Prefer this workflow over GitHub Sync fork. Sync fork follows upstream
mainhistory and can make the next stable run a deliberate no-op.
- Default channel
- Optional: repository secret
EDGE_EVER_CLOUDFLARE_DEPLOY_HOOK_URLtriggers a Cloudflare Deploy Hook after a successful push (useful when the Git integration misses a push). - Optional: re-run the workflow with force_redeploy to push an empty commit when Git is already current but Cloudflare needs another build.
- Build failure: inspect the Worker Deployments log and confirm the Deployment commit SHA matches Fork
main. - Scheduled update never runs: on a public Fork, enable Update deployed EdgeEver under Actions (scheduled workflows are disabled by default on forks, and may pause after long inactivity).