Maintainer console
Review requests, handle reports, ban, reserve and run maintenance, all from one place. Actions go privately to the bot: no comments, no slash commands. Each one is recorded in the audit log under your name.
GitHub only tells us who you are. We get no access to your account or repositories.
The console server isn't reachable right now. Use the token option below.
Or use a token (actions are posted as comments)
- Create a token on GitHub
Fine-grained · Only select repositories →
awesomeprojects.tech· Permissions: Issues read & write, Pull requests read & write, Discussions read.
New requests, last 30 days
Where names point
Most active, last 30 days
Latest
| Site | Owner | Status | Repo |
|---|
Bot settings. Each change goes through the bot as a commit to config.json, logged under your name.
| Name | Owner | Points at | Host |
|---|
Banned
Custom limits
Requests
Run now
Re-run the DNS deploy and website build, or the dangling-name check.
Reserved
Maintainers
Sites org
Re-apply the org's safe defaults, rulesets, Actions allow-list and maintainers team.
Bot account
Check the bot's token scopes and its role in the sites org.
Danger zone
For anything the console can't do: repository settings, Cloudflare, and the workflows (disable Subdomain bot to stop all automation).