Skip to content

docs(glitch-invaders): say how to make the Sentry token #40

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
theycallmeswift merged 1 commit into from
Nov 2, 2026
Merged

docs(glitch-invaders): say how to make the Sentry token #40

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion challenges/glitch-invaders/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,7 +112,11 @@ version:
| Auth | `bearer`, token `SENTRY_AUTH_TOKEN` |
| Host | `sentry.io` |

The token needs the `event:read`, `project:read`, and `org:read` scopes. The
The token needs the `event:read`, `project:read`, and `org:read` scopes, in
the org the game reports to. Make it with an internal integration under
**Settings > Custom Integrations** in that org, with Project, Issue & Event,
and Organization set to Read. An organization token won't do: its scopes are
fixed for CI and lack these. A token from another org gets `403`. The
station also needs a boothstrap that sets each `vault_services` credential in
the challenge's hooks. Release `0.1.0` predates that, so on it the challenge gets
no token and runs in demo mode.
Expand Down
Loading