Commit 0bed518
discord-feedback: don't require the Discord token when resume skips scraping
The Discord bot token was validated unconditionally at startup, before the
resume fast-path that re-attaches to an already-opened PR and only watches it.
That fast-path never touches Discord, so a fresh shell without the token (e.g. a
new screen window) couldn't resume a watch at all -- it died with
"DISCORD_BOT_TOKEN is not set" despite needing no Discord access.
Move the token requirement to point-of-use, right before the scrape. Resumes
that skip the scrape now run without it; a real scrape still fails fast with the
same clear message.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>1 parent 4f2d878 commit 0bed518
1 file changed
Lines changed: 7 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3389 | 3389 | | |
3390 | 3390 | | |
3391 | 3391 | | |
| 3392 | + | |
| 3393 | + | |
| 3394 | + | |
3392 | 3395 | | |
3393 | | - | |
3394 | | - | |
3395 | | - | |
3396 | | - | |
3397 | 3396 | | |
3398 | 3397 | | |
3399 | 3398 | | |
| |||
3486 | 3485 | | |
3487 | 3486 | | |
3488 | 3487 | | |
| 3488 | + | |
| 3489 | + | |
| 3490 | + | |
| 3491 | + | |
3489 | 3492 | | |
3490 | 3493 | | |
3491 | 3494 | | |
| |||
0 commit comments