Connecting GitHub
A token and a repository, no OAuth app to register.
Reports become GitHub issues with one click. Setup is two fields.
Create a token
A fine-grained personal access token with Issues: write on the repository you want issues in. Nothing else.
Fine-grained tokens are scoped to specific repositories, so this one cannot touch anything else in your account.
Connect it
On the project's settings page:
- Repository —
owner/repo, for exampleacme/website - Token — paste it once. It is stored and never shown again; paste a new one to replace it.
What lands in the issue
The reporter's description first, because that is what a developer reads. Then, in order and only when there is something to show:
- Where — the URL, the element selector, the element's text
- Environment — browser, OS, viewport, pixel ratio, language, time
- JavaScript errors — with timestamps
- Failed requests — status, method, URL, duration
- Console — warnings and errors only
- Screenshots — the reported element outlined in red
Screenshot links stay valid for a week, which is long enough for someone to open the issue, and short enough that a leaked issue body is not a leaked image archive.
The issue ends with a link back to the full report, where the images do not expire.
After it is sent
The report links straight to the issue, and its status moves from Reported to Confirmed on its own — someone has now looked at it.
Sending happens once. If you need a second issue from the same report, open the issue you already have.
Linear and Jira
Not built yet. The database has the column and the report formatter is tracker-agnostic; only the GitHub client exists.