chore(screenshots): add Git LFS tracking for screenshot ground truths#31077
Draft
chore(screenshots): add Git LFS tracking for screenshot ground truths#31077
Conversation
Track Playwright screenshot PNGs with Git LFS to prevent GitHub's large file push rejection (GH001). Uses going-forward-only strategy so existing clones and forks are unaffected.
|
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
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.
Track Playwright screenshot PNGs with Git LFS to prevent GitHub's large file push rejection (GH001). Uses going-forward-only strategy so existing clones and forks are unaffected.
Issue number: resolves #
What is the current behavior?
GH001: Large files detected. You may want to try Git Large File Storage.gitdirectory has grown to ~1.6 GB due to 19,000+ historical PNG blobs across 6,700+ committed screenshots.What is the new behavior?
core/src/components/**/*-snapshots/*.png) are tracked with Git LFS via.gitattributestest-core-screenshotandupdate-reference-screenshots) uselfs: trueonactions/checkoutto download real PNG content before running Playwright comparisonsDoes this introduce a breaking change?
Other information
Strategy: Going-forward only (no history rewrite). Existing clones and forks continue to work. Contributors need
git lfs install(one-time setup) to work with screenshot files.Files changed:
.gitattributes— LFS tracking rule for snapshot PNGs.github/workflows/build.yml—lfs: trueontest-core-screenshotcheckout.github/workflows/update-screenshots.yml—lfs: trueon both screenshot job checkoutsdocs/core/testing/usage-instructions.md— new "Git LFS Setup" sectiondocs/CONTRIBUTING.md— Git LFS as prerequisite step in Setup