How to recover lost LHCI_GITHUB_APP_TOKEN
See original GitHub issueIs there any way to find the LHCI_GITHUB_APP_TOKEN
once you close the authorization confirmation page? 😄
I can’t find it in the documentation. This would be a good question to add to the FAQ.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (1 by maintainers)
Top Results From Across the Web
How to fix "Must provide token for LHCI target" · Issue #144
Done running Lighthouse! Checking assertions against 1 URL(s), 2 total run(s). All results processed! Error: Must provide token for LHCI target
Read more >Token expiration and revocation
If a valid OAuth token, GitHub App token, or personal access token is pushed to a public repository or public gist, the token...
Read more >lighthouse-ci/configuration.md at main
If you've forgotten your token, connect directly to your server and run lhci wizard --wizard=reset-build-token .
Read more >Redirected to this repo when trying to get token ...
Hi, I'm trying to retrieve a token for a private repo we have in our ... The GitHub app requires an OAuth callback...
Read more >GitHub Apps - Lighthouse CI
Copy the token provided on the authorization confirmation page and add it to ... install -g @lhci/cli@0.6.x - run: npm run build -...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey folks sorry for the troubles here! A couple notes:
LHCI_GITHUB_APP_TOKEN
or--githubAppToken
not--githubToken
orLHCI_GITHUB_TOKEN
, and vice-versa if you’re using direct status checks with a personal GitHub access token. There are two different methods of status check support and accidentally using the wrong flag/token leads to the 422 error. We’ll try to make this clearer in the docs.I believe you need to remove the app from Github and then reinstall it