feat(deploy): #vacation-deploy agent merges branch into main, then deploys prod#10
Draft
ether314 wants to merge 1 commit into
Draft
feat(deploy): #vacation-deploy agent merges branch into main, then deploys prod#10ether314 wants to merge 1 commit into
ether314 wants to merge 1 commit into
Conversation
The deploy agent now merges the feature branch into main, pushes main, then deploys main to the Firebase prod project (vacation-app-21706). Adds scripts/merge-and-deploy.sh (with DRY_RUN + PR-number support) and documents the flow in docs/deploy.md. Co-authored-by: Joe M <[email protected]>
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
2 participants
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.
Summary
Modifies the
#vacation-deployagent flow so it performs a single two-step operation: merge the feature branch intomain, then deploymainto the Firebase prod project (vacation-app-21706). Previously the deploy agent only deployed an already-merged commit (and was blocked on Firebase auth).scripts/merge-and-deploy.sh— the canonical entrypoint: fetch → checkout/ffmain→ merge branch (or PR head) → pushmain→ deploy (hostingby default,functionsoptional).scripts/merge-and-deploy.sh <branch>or<pr-number>(resolves PR head viagh), plusDEPLOY_TARGETS,FIREBASE_PROJECT,MAIN_BRANCH, andDRY_RUNenv knobs.docs/deploy.md.Auth uses the already-provisioned
FIREBASE_TOKENCloud Agent secret. On a merge conflict the script stops before pushing/deploying.Testing
Validated every stage that can be exercised without mutating
mainor production. I deliberately stopped short of a livegit push origin main+ prod deploy, since those are irreversible production actions — the flow is ready to run via#vacation-deploy(orscripts/merge-and-deploy.sh) on your go-ahead.bash -n scripts/merge-and-deploy.sh— syntax validgh pr view 9 --json headRefName— PR-number → branch resolution worksDRY_RUN=1 scripts/merge-and-deploy.sh <branch>in an isolated clone — clean merge commit, push/deploy correctly skippedfirebase projects:list --token $FIREBASE_TOKEN— authenticates tovacation-app-21706flutter build web -t lib/main_customer.dart --release— prod build compiles (the deploy step's build)