search

foo-software / lighthouse-check-action

GitHub Action for running @GoogleChromeLabs Lighthouse audits with all the bells and whistles 🔔 Multiple audits, Slack notifications, and more!
https://github.com/marketplace/actions/lighthouse-check
MIT License
478 stars 24 forks source link

Error: All URLs failed to be enqueued. #73

Closed willpaige closed 2 years ago

willpaige commented 2 years ago

Hi, this is probably more of a human error. That said, I cannot get it to run as it keeps failing on the above, from what I can see the URL does exist. Screenshot 2021-12-13 at 4 23 22 pm

Screenshot 2021-12-13 at 4 24 25 pm

Note: I originally tried with just url: 'https://www.test.rooster.money/gb/' but received a similar error.

Kindly appreciate any help with this!

Will

adamhenson commented 2 years ago

Hi @willpaige - ya, sorry this is confusing. I want to find a better way to make things clearer in the docs. Your best bet is to follow the example, but I could see how even that is confusing.

I think you need the equivalent of this from the docs:

        with:
          fooApiToken: 'myApiToken'
          urls: 'myPageToken1,myPageToken2'

I believe you can use urlsJson, but instead of a list of URLs, these need to be a list of "page API tokens". It's the last item that is blocked off in your screenshot.

Please let me know if that fixes your issue and we can close this... otherwise, you can provide the error message.

willpaige commented 2 years ago

Ahh I see, I was following the quick start https://github.com/foo-software/lighthouse-check-action. Screenshot 2021-12-13 at 5 07 03 pm

That's worked for me, just need to fix another user setup error now 😄

adamhenson commented 2 years ago

Right, ya I know it's confusing. When running this GitHub Action on its own (not against Foo's API), you would use the actual URLs. It will probably make sense in the near future to add a separate, additional field like pageIds, so it's not as confusing.