-
-
Notifications
You must be signed in to change notification settings - Fork 900
fix: ligthouse check failure fix #4062
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
WalkthroughThe workflow file for Lighthouse CI in the GitHub Actions configuration has been updated to use newer versions of its dependencies. Specifically, the Changes
Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: .coderabbit.yaml 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 180000ms (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
✅ Deploy Preview for asyncapi-website ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4062 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 22 22
Lines 778 778
Branches 144 144
=========================================
Hits 778 778 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (2)
.github/workflows/lighthouse-ci.yml (2)
38-38
: Verify compatibility for actions/checkout@v4
actions/checkout v4 introduces changes to defaults (e.g.,fetch-depth
) and new features. If any downstream step relies on full Git history (tags, full commit logs, submodules, etc.), consider explicitly setting:- uses: actions/checkout@v4 with: fetch-depth: 0Otherwise a shallow clone may lead to unexpected behavior.
51-51
: Consider using a semantic version tag for treosh/lighthouse-ci-action
Pinning to a commit hash (2f8dda6cf4d…
) guarantees immutability but can be less readable. For clarity, you may switch to the official release tag:uses: treosh/[email protected]or
uses: treosh/lighthouse-ci-action@v10If stability is your top priority, the existing commit pin is also acceptable.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
.github/workflows/lighthouse-ci.yml
(2 hunks)
⏰ Context from checks skipped due to timeout of 180000ms (4)
- GitHub Check: Redirect rules - asyncapi-website
- GitHub Check: Header rules - asyncapi-website
- GitHub Check: Pages changed - asyncapi-website
- GitHub Check: Lighthouse CI
@asyncapi/bounty_team |
@sambhavgupta0705 The workflow is still failing in CI. Will that be resolved post-merge? Can you please share a link to the workflow passing in your forked repository? |
Hey |
@@ -35,7 +35,7 @@ jobs: | |||
run: echo "shouldrun=true" >> $GITHUB_OUTPUT | |||
|
|||
- if: steps.should_run.outputs.shouldrun == 'true' | |||
uses: actions/checkout@v3 | |||
uses: actions/checkout@v | |||
|
|||
- if: steps.should_run.outputs.shouldrun == 'true' | |||
name: Await Netlify Preview |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sambhavgupta0705 Are we sure that it is waiting for netlify deployment to complete? Also, what if netlify deployment fails on latest commit?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please look into the workflow again? It is still failing in your PR. You can also look into a completely different approach to get Lighthouse results.
##3842
Summary by CodeRabbit