feat: three-environment web deploy strategy (staging/beta/production) - #48
Merged
Merged
Conversation
Add the in-repo scaffolding for CF Pages-driven staging/beta/production deploys: a parameterized bin/cf-build.sh build script, an auto-tag + changelog GH Actions workflow (ported from my-ai-team's release helpers), a new .env.beta pointed at the production API, and an ENV_NAME-driven app bar label so non-production builds are always visibly marked. The GH Pages staging workflow is retired in favor of the CF Pages Git integration; the manual GH Pages production release is untouched. CF Pages project creation, DNS records, and GCP OAuth origins are external dashboard/API actions tracked separately and out of scope here. Closes #47
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #47