Lighthouse-ci: How to recover lost LHCI_GITHUB_APP_TOKEN

[mauriciabad]

Is 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.

[ascorbic]

I believe you need to remove the app from Github and then reinstall it

[mauriciabad]

Thanks, I have it again.

[mauriciabad]

Now that I have it, the status isn't being updated. 😢

This is the log:

GitHub token found, attempting to set status...
GitHub responded with 422
{"success":false}

Any ideas why?

[Fumler]

Now that I have it, the status isn't being updated. 😢

This is the log:

GitHub token found, attempting to set status...
GitHub responded with 422
{"success":false}

Any ideas why?

We're having the same problem in a private repo. Gave the github app org access to only the specific repo, but it's not working, with the exact same error.

[ascorbic]

I'm having the problem too.

[patrickhulce]

Hey folks sorry for the troubles here! A couple notes:

1. Sounds like a few of you are already know this, but some logs suggest it's worth noting again... If you're using the GitHub App you need to be using the LHCI_GITHUB_APP_TOKEN or --githubAppToken not --githubToken or LHCI_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.
2. We were being a little too strict about what URLs you're allowed to link to from the status checks which also leads to 422. We just pushed an update to the app service that should fallback to a generic docs link in this situation, so things should be working here now as well.
3. There's no way to retrieve the token if you've lost it. Just uninstalling and reinstalling the app is the right move. We'll add this to the FAQs 👍