Testers can use beta features in servers whose owner opted in.
- `beta.Configure` takes the opted-in servers; testers are looked up in the beta server, so a role with the same ID elsewhere means nothing. Fails closed.
- Beta commands are registered per opted-in server and removed when it opts out (`/beta` stays in the beta server).
- `beta.ServerEnabled` for behaviour no person triggers.
- Docs updated.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
- beta.Configure takes the opted-in servers; testers are looked up in the beta server
- beta commands registered per opted-in server and removed when it opts out
- beta.ServerEnabled for behaviour that no person triggers
- docs updated
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
The bot remembers where it registered beta commands (beta_registered) and
removes them from servers that are no longer in the beta at the next start.
Failed cleanups are retried; a server the bot has left is forgotten.
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Testers can use beta features in servers whose owner opted in.
beta.Configuretakes the opted-in servers; testers are looked up in the beta server, so a role with the same ID elsewhere means nothing. Fails closed./betastays in the beta server).beta.ServerEnabledfor behaviour no person triggers.🤖 Generated with Claude Code