Automate primary production deployments from main
This commit is contained in:
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user