Skip to content
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

meta: skip lighthouse CI when no vercel preview detected #7266

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

RedYetiDev
Copy link
Member

Description

This changes the Lighthouse CI to skip when a Vercel preview is not detected

Related Issues

#7253

Signed-off-by: Aviv Keller <[email protected]>
@RedYetiDev RedYetiDev requested a review from a team as a code owner November 20, 2024 21:28
Copy link

vercel bot commented Nov 20, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
nodejs-org ✅ Ready (Inspect) Visit Preview Nov 20, 2024 9:28pm

@RedYetiDev
Copy link
Member Author

The commit message didn't save 🤔, regardless, the PR title will be used, right? If not, feel free to force push and fix it.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 1 out of 1 changed files in this pull request and generated no suggestions.

@RedYetiDev
Copy link
Member Author

image
Without a Vercel preview, the Lighthouse CI is skipped, as shown above.

${{ needs.get-vercel-preview.outputs.url }}/en/about
${{ needs.get-vercel-preview.outputs.url }}/en/about/previous-releases
${{ needs.get-vercel-preview.outputs.url }}/en/download
${{ needs.get-vercel-preview.outputs.url }}/en/blog
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

need to add learn here

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't that be a followup, given that this is specifically for skipping the workflow?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this list was semi-intelligently designed not to be exhaustive of all pages, but to try to hit the major features

  • homepage (global)
  • markdown rendering (about)
  • previous-releases (the release data / table)
  • download (release data / os detection / lots of complexity)
  • blog (blog data / rendering)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Imo we should test the learn section to ensure everything is right. Yeah it's look like about but it's not same eg there are avatars in the learn page

@@ -27,12 +27,39 @@ permissions:
pull-requests: write

jobs:
lighthouse-ci:
get-vercel-preview:
# We want to skip our lighthouse analysis on Dependabot PRs
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this comment needs to move with the ordering

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean? It's commenting on the line below (skipping the Dependabot).

${{ needs.get-vercel-preview.outputs.url }}/en/about
${{ needs.get-vercel-preview.outputs.url }}/en/about/previous-releases
${{ needs.get-vercel-preview.outputs.url }}/en/download
${{ needs.get-vercel-preview.outputs.url }}/en/blog
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this list was semi-intelligently designed not to be exhaustive of all pages, but to try to hit the major features

  • homepage (global)
  • markdown rendering (about)
  • previous-releases (the release data / table)
  • download (release data / os detection / lots of complexity)
  • blog (blog data / rendering)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants