ci(miniapp/roebel-data): auto-sync to deploy repo + DEPLOY.md - #16
Open
MaxBrych wants to merge 1 commit into
Open
ci(miniapp/roebel-data): auto-sync to deploy repo + DEPLOY.md#16MaxBrych wants to merge 1 commit into
MaxBrych wants to merge 1 commit into
Conversation
The live app builds from the standalone MaxBrych/netizen-roebel-data repo (not the monorepo). Add a workflow mirroring src/ + public/ into that repo on main pushes touching apps/mini-apps/roebel-data, and document the real deploy chain + the one-time Vercel Production-Branch setting. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Sets up automatic propagation of
roebel-datamini-app changes to production, and documents the (non-obvious) deploy chain.Why: the live mini-app builds from a separate standalone repo (
MaxBrych/netizen-roebel-data), which thenetizen-roebel-dataVercel project is git-connected to — not this monorepo. So monorepomainmerges never reached it. This automates the bridge.Adds
.github/workflows/sync-roebel-data-miniapp.yml— on push tomaintouchingapps/mini-apps/roebel-data/**, mirrorssrc/+public/into the deploy repo and pushes → Vercel builds.apps/mini-apps/roebel-data/DEPLOY.md— the full chain (monorepo → deploy repo → Vercel →mini_apps.home_url→ Expo host), plus the manual-sync fallback and the "reconnect Vercel to the monorepo" alternative.One-time setup to activate (in DEPLOY.md): add a
NETIZEN_ROEBEL_DATA_DEPLOY_TOKENsecret (fine-grained PAT, Contents:write onMaxBrych/netizen-roebel-data) and set the Vercel project's Production Branch = main.Supersedes #15 (same DEPLOY.md, now accurate + the workflow).
🤖 Generated with Claude Code