chore: Update danger token

[eps1lon]

Part of #395

Created a new account. Will share credentials in an internal team discussion. Followed the official docs in which we don't need a separate token apparently.

[orta]

This'll only work for same branch PRs because of the GH actions security settings, so it's not a reasonable answer I'm afraid though danger/danger-js#1125 should fix it, it needs a new token, looks like someone got that public token revoked

[swyxio]

i maybe dont fully understand this but don't Github actions themselves have access to Checks API/their own token for doing whatever? anyway i'm standing by to do whatever needed if i need to add a Personal Access Token via secrets i can do that

[eps1lon]

should fix it, it needs a new token, looks like someone got that public token revoked

@orta I did add a new token with public_repo in 74c4fe7 (#396) but that failed as well: https://github.com/typescript-cheatsheets/react/runs/2128883490

[eps1lon]

@orta Any idea why the new token is insufficient? Is https://danger.systems/js/guides/getting_started.html#tokens-for-oss-projects still up-to-date?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!