You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to integrate it into the repo, there is a preparation to make. This app is needed to be installed into the repo.
However, there is a warning with that method. They share the private key used in the checks API.
Taken from their source code:
/**
* Before you say anything I *know* this is horribly insecure.
*
* If we were not to to this then every user would have to create
* their own GitHub App and manage the APP_ID and PRIVATE_KEY through
* env vars.
*
* How could this go wrong? Well this PRIVATE_KEY only creates jwt
* tokens that work on people who have installed the Jest Results
* App. If an attacker got ahold of the token they could only read repo
* metadata and read/write checks. So the attack surface is really only
* messing with a users checks, which is not too risky.
*/
We can avoid using this method by creating our own github app as stated here. But it will be beneficial only if we can securely handle env vars in circleci (or github actions).
That being said, I don't mind doing the code changes.
https://github.com/hipstersmoothie/jest-github-reporter
The text was updated successfully, but these errors were encountered: