Automate primary production deployments from main

This commit is contained in:
Kevin
2026-09-02 10:47:46 -04:00
parent 1b25dc37a6
commit 954b230d05
5 changed files with 31 additions and 18 deletions
+4 -3
View File
@@ -33,9 +33,10 @@ routes, account IDs, or secrets.
## Preview deployment
The Gitea workflows deploy scoped non-production Workers from the pilot and
Markdown-test branches: `3031023-xyz-www-preview` for primary-site changes and
`3031023-xyz-blog-preview` for blog changes.
The Gitea workflows deploy scoped non-production Workers from every non-`main`
branch: `3031023-xyz-www-preview` for primary-site changes and
`3031023-xyz-blog-preview` for blog changes. Relevant primary-site pushes to
`main` deploy the existing `3031023-xyz-www` production Worker automatically.
It uses the existing `CF_API_TOKEN` and `CF_ACCOUNT_ID`. The token retains the
Pages permissions needed for the `main` rollback target and now also permits
the non-production Worker preview deployment.