Repository navigation
Run Lighthouse only where it measures something new - #7
Merged
Merged
Conversation
Skipped on pushes to master: branch protection requires an up-to-date pull request, so the merge commit is what that pull request measured. Skipped on pull requests that only touch files the deployed site does not contain (profile/, .claude/, README.md, git config, the profile sync workflow). Unknown paths count as relevant, manual runs always measure. 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.
Lighthouse is the slowest CI step (about 1.5 of 2.5 minutes). This limits it to runs where it can find something new. All other checks run unchanged.
When Lighthouse runs
profile/,.claude/,README.md,.gitignore,.gitattributesor.github/workflows/sync-profile-readme.yml. Unknown paths count as relevant, so a new file type never slips past by accident.strict: true, enforced for admins too), so the merge commit is exactly what that pull request already measured. The deploy job still waits forvalidate.workflow_dispatch): always measures.How
fetch-depth: 2, so the PR merge commit has its base as first parent;git diff --name-only HEAD^1 HEADlists the PR's changes.if:on that output.Checks
validate.yml, so Lighthouse should run on it, which exercises the "run" path in CI. The "skip" path shows on the next profile-only PR.🤖 Generated with Claude Code