Repository navigation
Select and verify affected Netlify previews before URL tests - #25
Merged
Merged
Conversation
silveltman
changed the title
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
1 participant
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.
URL tests currently wait for every Netlify site while holding shared preview accounts and spending their test budget. Resolve matching previews in a separate job before Web installation and its account lock.
Monorepos can pass deployment metadata to select affected sites using their existing Netlify build.ignore rules against the cumulative PR diff. Reuse a skipped preview only when its published revision is an ancestor with unchanged build inputs. Static websites can explicitly permit verified production fallback; signed-in apps require an isolated preview. Web rechecks both the PR and the approved deployment revisions immediately before testing.
The Test aggregate accepts skipped Web only for an explicitly empty selection. Existing callers remain compatible, and production execution stays unchanged.
Validation: 49 workflow behavior tests pass, including real Git history, shared dependencies, app base paths, renames/deletions, later unrelated pushes, stale/cancelled builds, and deployment changes while queued. Independent review found no remaining material issues.