Skip to content

Commit f69d99a

Browse files
authored
Added lighthouse badger token info to FAQ --------- Signed-off-by: George Araújo <[email protected]>
1 parent 53fb011 commit f69d99a

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

FAQ.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,7 @@ Here are some frequently asked questions. If you have a different question, plea
99
- [Atom feed doesn't work. Why?](#atom-feed-doesnt-work-why)
1010
- [My site doesn't work when I enable `related_blog_posts`. Why?](#my-site-doesnt-work-when-i-enable-related_blog_posts-why)
1111
- [When trying to deploy, it's asking for github login credentials, which github disabled password authentication and it exits with an error. How to fix?](#when-trying-to-deploy-its-asking-for-github-login-credentials-which-github-disabled-password-authentication-and-it-exits-with-an-error-how-to-fix)
12+
- [When I manually run the Lighthouse Badger workflow, it fails with `Error: Input required and not supplied: token`. How do I fix that?](#when-i-manually-run-the-lighthouse-badger-workflow-it-fails-with-error-input-required-and-not-supplied-token-how-do-i-fix-that)
1213

1314
---
1415

@@ -39,3 +40,7 @@ This is probably due to the [classifier reborn](https://github.com/jekyll/classi
3940
#### When trying to deploy, it's asking for github login credentials, which github disabled password authentication and it exits with an error. How to fix?
4041

4142
Open .git/config file using your preferred editor. Change the `https` portion of the `url` variable to `ssh`. Try deploying again.
43+
44+
#### When I manually run the [Lighthouse Badger](https://github.com/alshedivat/al-folio/actions/workflows/lighthouse-badger.yml) workflow, it fails with `Error: Input required and not supplied: token`. How do I fix that?
45+
46+
You need to [create a personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-fine-grained-personal-access-token) and [add it as a secret](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#creating-encrypted-secrets-for-a-repository) named `LIGHTHOUSE_BADGER_TOKEN` to your repository. For more information, check [lighthouse-badger documentation](https://github.com/MyActionWay/lighthouse-badger-workflows#lighthouse-badger-easyyml) on how to do this.

0 commit comments

Comments
 (0)