My lighthouse action is setting GitHub status, but no artifacts or performance details. Why?

[MarkBennett]

Hi! Thanks for this great tool!

I've followed the Getting Started Guide and created a GitHub Action workflow, along with authorizing and installing the GitHub App in my repository and setting the LHCI_GITHUB_APP_TOKEN in my project environment, but I'm not seeing any of the status details (performance numbers) or a link to the artifact in my build.

As we're just starting out and our numbers aren't great, I'd like to focus on tracking these for now rather than adding an assertion and failing the build.

Here is my workflow file:

name: Lighthouse CI for Netlify sites
on: pull_request
jobs:
  build:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v2
      - name: Use Node.js 12.x
        uses: actions/setup-node@v1
        with:
          node-version: 12.x
      - name: Wait for the Netlify Preview
        uses: jakepartusch/wait-for-netlify-action@v1
        id: netlify
        with:
          site_name: 'clhbid-com'
      - name: Run Lighthouse CI
        run: |
          npm install -g @lhci/cli@0.6.x
          lhci autorun --collect.url=${{ steps.netlify.outputs.url }}
        env:
          LHCI_GITHUB_APP_TOKEN: ${{ secrets.LHCI_GITHUB_APP_TOKEN }}

And here is my lighthouserc.js:

module.exports = {
  ci: {
    upload: {
      target: 'temporary-public-storage',
    },
  },
};

This is what my projects environmet looks like:

Is anyone able to spot what's wrong? The Lighthouse job step looks good, and it's setting the GitHub status properly just without details or a link to the report. This is a typical run output.

Run npm install -g @lhci/cli@0.6.x
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
/opt/hostedtoolcache/node/12.20.0/x64/bin/lhci -> /opt/hostedtoolcache/node/12.20.0/x64/lib/node_modules/@lhci/cli/src/cli.js
+ @lhci/cli@0.6.1
added 423 packages from 266 contributors in 13.321s
✅  .lighthouseci/ directory writable
✅  Configuration file found
✅  Chrome installation found
✅  GitHub token set
Healthcheck passed!

Running Lighthouse 3 time(s) on https://deploy-preview-106--clhbid-com.netlify.app
Run #1...done.
Run #2...done.
Run #3...done.
Done running Lighthouse!

Uploading median LHR of https://deploy-preview-106--clhbid-com.netlify.app/...success!
Open the report at https://storage.googleapis.com/lighthouse-infrastructure.appspot.com/reports/1608143721623-80075.report.html
GitHub token found, attempting to set status...
GitHub accepted "success" status for "lhci/url/".

Done running autorun.

This what my check looks like in the UI. Note the lack of details or the annotations.

Thank you so much in advance! 🍻

[patrickhulce]

Hey @MarkBennett thanks for sharing :)

The LHCI GitHub App sets the status on the pull request / commit level and isn't aware of GitHub actions specifically (it can be used with any CI provider). If you go to your pull request or commit details, do you see the LHCI "Details" link? It should look like the below.

If you're interested in a GitHub Actions specific solution that stores the data as artifacts instead of the public storage. You can take a look at solutions from the community like https://github.com/treosh/lighthouse-ci-action

[v-dimitroff]

Well I have the same issue and I do want my lhci to run on PR's actions only. Is there a way to show checks inside the PR, maybe with replacing the LHCI_BUILD_CONTEXT env variables?

[MarkBennett]

Sorry for ghosting on this! I missed the notifiaction and we've switched to tracking our performance using Sentry.io instead.

You can close as we've found a different solution, but it sounds like others are still affected.

[asgerjensen]

+1 for this

[lpeabody]

Another +1 for this.

[lpeabody]

Adding the following to my workflow allowed the status check to be posted against the pull request:

env:
  LHCI_BUILD_CONTEXT__CURRENT_HASH: ${{ github.event.pull_request.head.sha || github.sha }}

EDIT: I imagine this is fine to do if you're just using temporary public storage. But, I think if you're trying to send results to a Lighthouse CI Server instance, this might cause problems. I have no tests to validate this, but it's something to consider and watch out for.