Repository navigation
fix(ci): demo site deploys once a day, and build branches stop failing on Vercel - #338
Merged
Merged
Conversation
…g on Vercel The backoffice Vercel project built every pushed branch: develop for backoffice.demo.place.tech, each feature branch as a preview, and each build/* branch, which always failed. All of them count toward the PlaceOS team's daily deployment limit, which other projects share. - vercel.json: turn off Vercel deployments for all branches except backoffice-demo - BUILD workflow: add a vercel.json that turns off deployments to each build/* branch commit, because Vercel reads it from the pushed commit - Demo Site workflow: move backoffice-demo to develop once per day, only if develop changed Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
The
backofficeVercel project builds every pushed branch, and each deployment counts toward the PlaceOS team's daily Vercel limit, which all projects share. In the last week it made 8 deployments:developfor backoffice.demo.place.tech, a preview for each feature branch push, and one for eachbuild/devpush. Thebuild/devdeployments always fail, because that branch holds only the compiled app.user-interfaceshad the same problem (PlaceOS/user-interfaces#686), which used up the limit.Now Vercel only deploys a
backoffice-demobranch, and a daily workflow moves that branch todevelopwhendevelopchanged. That is at most one deployment per day.vercel.json: turn off Vercel deployments for all branches exceptbackoffice-demo.BUILDworkflow: before each publish, add a one-linevercel.jsonthat turns off deployments to thebuild/*branch commit. Vercel readsvercel.jsonfrom the pushed commit, and build branches do not contain the root file. Build branches get this one extra file.Demo Siteworkflow: runs daily at 17:00 UTC, or manually from the Actions tab.After merge (Vercel settings)
backoffice-demo(Settings → Environments → Production → Branch Tracking). backoffice.demo.place.tech follows the production branch.Demo Siteworkflow once to create the branch.backoffice-dev.demo.place.techpoints to the oldrefactor/layoutbranch. After this change it gets no new deployments. Remove it, or keep it as is.Tests
Demo Siteworkflow step, taken from the YAML, against a local bare repo from a shallow clone: it creates the branch, skips whendevelopdid not change, and moves the branch after a new commit.BUILDstep: it writes valid JSON. Prettier passes.Created with Claude Opus 5.5 in Claude Code.
🤖 Generated with Claude Code