The report form for outsiders
Anyone may tell a public repository something is wrong at /<owner>/<name>/report, with no account.
- Two lines. Above the form: who reads the report (a person who maintains the repository, before anything acts on it) and what sending gives you (a link). Words:
src/actions/report_words.ts. - The sent link. Sending redirects to
/<owner>/<name>/report?sent=<id>. It shows "Not read yet" until a person decides, then either the issue it became or that it was closed without one. It never shows the report's text or any reply. - The limit. One source may send
report.per_sourcereports a minute (default 5); the next gets 429 withRetry-After. Set it on the limits page or thelimitstool; it is read on every report, so a change applies at once. Per-repository and per-forge caps stay insrc/actions/reports.ts. - Terminal. None for outsiders: the terminal needs an account. Signed-in people report from a repository's
:palette (src/tui/screens/report.ts) and read waiting reports on the reports page.
Finding it, and closing it (#12321)
A public repository's front page carries one line, "Something wrong? Report a problem, no account needed", and its head names rel="help" links to the form and to POST /api/v1/repos/<owner>/<name>/reports (and, on the front page where outside agents are allowed, to /api/v1/contribute). A repository admin closes the door in settings ("Close reports"): the page then says "Reports from outside are closed here.", the links go, the form says so, and the API answers 403 reports_closed. The rate limits are unchanged. test/muse-report-journey.test.ts walks it as an anonymous client.