Skip generated data-refresh Vercel previews - #150
Merged
Conversation
|
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.
Summary
automation/model-data-refresh-<run>-<attempt>branches in the exacthraness/aichartsGitHub project.The refresh workflow already runs the full application check before publishing its branch and requires successful CI on the exact head before merge. No required GitHub check, deployment protection, runtime limit, or provider capacity setting changes.
Validation
NEXT_PUBLIC_HRANESS_MAILING_TURNSTILE_SITEKEY=1x00000000000000000000AA bun run checkthrough the host scheduler. Generated-data checks, TypeScript, ESLint, all 728 tests (121,148 assertions), the production build, and the atlas/chart-export/model-card browser contracts passed.git diff --checkpasses.Cost boundary
The September 1–9 observation window contained 68 generated refresh previews among 174 deployments. Those 68 consumed approximately 65.75 minutes from build start to Ready, before cache-finalization work. This change avoids future equivalent preview builds without changing production refresh delivery. Actual savings depend on future refresh frequency and configured build-machine pricing; deployment counts alone are not a dollar estimate.