lighthouse-badger-easy Input required and not supplied: token

[Salih2000]

Hey I added my token on secrets as named on the code but I still get this error, Can you pls help me what's wrong here ?

[george-gca]

No idea why considering that the token has the right properties. Have you checked their repo to see if anything changed recently, or if there are any issues about this?

[Salih2000]

Well while creating my token, I configured the settings accordingly to this screenshot . I also conducted thorough research to find any up-to-date solutions for this issue. Unfortunately, I only found topics that were unrelated or too old to my specific problem.

[george-gca]

Follow the steps in our FAQ about that. I recommend you creating a PAT (fine-grained) with the scopes and permissions suggested for the lighthouse-badger-easy.yml.

[matinator]

I did as PAT as required, but still it doesn't find it in the github action, any news on how to possibly fix it?

[matinator]

Thank you for your quick reply. I will try to comeback to this theme when it works.

[Salih2000]

I will be very happy if you solve that out and share with the community.

[matinator]

I will happily do that if I am able to find a solution, but it depends mainly to find a workaround of github and that can be quite difficult.

[matinator]

Solved it in the end, it was easier than I thought, I only had to change the worflow at line 53 of lighthouse-badger.yml with:

token: ${{ secrets.LIGHTHOUSE_BADGER_TOKEN }}

instead of the original one

[Salih2000]

this change solved my problem. My page is live now, thank you very much for your help, Grazie!

[george-gca]

This is weird, because it doesn't throw error on the main repo. But indeed this line uses a param that is not defined. I will updated it accordingly.

[george-gca]

Also note that this workflow is not needed to deploy the site, only to evaluate its speed and compliance to some standards.

[Salih2000]

On https://github.com/alshedivat/al-folio/blob/master/INSTALL.md page, there is a video manual. If you open it, you can observe the error at the 2:01 mark in the timeline. Thank you for your contribution.