ci: cut Site over to CircleCI (remove Forgejo Actions, live deploy) #19
No reviewers
Labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Site!19
Loading…
Reference in a new issue
No description provided.
Delete branch "ci/cutover"
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?
Merge after #18 (this branch is stacked on it; the diff shows #18's commits until #18 merges).
Why
Cutover: CircleCI has been running Site's checks, previews and a dry-run deploy alongside Forgejo Actions. This makes CircleCI the only CI and the live deployer.
What changed
.forgejo/workflows/deploy.ymlandpreview.yml(Site's only Forgejo workflows) and the actionlint wiring that linted them (.forgejo/actionlint.yaml, the lint step, the actionlint pin).release_dry_run: falsefor pushes to main, sodeployrunswrangler deploywith thecloudflare-prodcontext (main only), between asite-productiondeploy marker plan and its SUCCESS/FAILED update. The manual API dry run is unchanged.docs/ci.md, CONTRIBUTING: CircleCI deploys main; same-repo previews come from the stickyci: previewlabel; fork PRs get the artifact preview afterci: approved. Forgejo's one-shotpreviewlabel is no longer used.Testing
circleci config validate, the orb's conftest policies (16 pass), one workflow per event,mise run lint,mise run test. Live on merge: see the checklist below.After merge
deploylogswrangler deploy, asite-productionmarker goes to SUCCESS in CircleCI's Deploys,gateis green./version.json.release_dry_runback totruefor setup-main.9446cfca71768cd5338bPreview: https://pr-19-magicbean-site.hckr-5e0.workers.dev
This commit (
768cd5338b) on its own: https://5ad8aaf6-magicbean-site.hckr-5e0.workers.dev