Repository navigation
chore(marketing): skip Vercel builds that do not touch the site - #662
Conversation
|
Deployment failed for project pylon-marketing with the following error: Learn More: https://vercel.com/pylon-code?upgradeToPro=build-rate-limit |
|
Merging with the Vercel preview check red: it failed with |
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
What
The marketing site's Vercel config gets an
ignoreCommand: a build is skipped unlessapps/marketing,packages/shared(its one workspace dependency), or the lockfile changed since that branch's last deployment.Why
apps/marketing/vercel.tshas git deployments on and no ignore rule, so Vercel built a preview on every push to every pull request branch and a production build on every merge. On 2026-09-18 there were 39 pull requests, most pushed several times, for a site whose own code last changed five commits ago. The account hit Vercel's build rate limit: the Vercel check then failed on unrelated pull requests with abuild-rate-limitlink, previews sat "deploying" for 40 minutes, and the release workflow's hosted-app deploy timed out four times (#655).The hosted app (
apps/web) already has git deployments off and is deployed only by the release workflow, so it needs no change here.How
git diff --quiet "${VERCEL_GIT_PREVIOUS_SHA:-HEAD^}" HEAD -- . ../../packages/shared ../../pnpm-lock.yaml ../../pnpm-workspace.yaml, run from the project rootapps/marketing. Exit 0 skips the build. If the previous SHA is not in Vercel's shallow clone, git fails with a non-zero code, which builds: the safe default.Verification
@t3tools/marketing: 0 errors;ignoreCommandis in@vercel/config'sVercelConfigtype.vp checkclean.Not addressed here
The release workflow deployed the hosted app 11 times that day (4 scheduled, 7 manual). Those are real deploys, not waste, but they share the same quota; dispatching one nightly for a batch of merges rather than one per merge keeps it down.
Closes part of #655.
Model: Claude Fable 5.1, in Pylon via the Claude Code harness.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.