Screendog files GitHub issues via the REST API — no marketplace app.
Connect GitHub once with a fine-grained personal access token scoped to a single repo. Every recording becomes a GitHub issue with title, body, and the recording link, created via `POST /repos/:owner/:repo/issues`.
| Capability | Status |
|---|---|
| Live REST integration | Yes — `POST /repos/:owner/:repo/issues` |
| Fine-grained PAT supported | Yes — scope to one repo |
| Classic PAT supported | Yes — `repo` scope |
| GitHub App installation required | No |
| Two-way sync (issue close → recording status) | No — file-and-forget |
How it works
In `/<workspace>/settings`, paste a GitHub PAT and the repo as `owner/repo`. Click File to GitHub from any recording. Screendog calls the REST endpoint server-side, attaches the share URL, and returns the issue URL.
Token recommendations
We recommend a fine-grained PAT scoped to a single repo with Issues: Read and Write. Classic tokens with the `repo` scope work too.
What if my repo is on GitHub Enterprise Server?
undefined
Frequently asked
Why not a GitHub App?
PATs are simpler for individual contributors. A GitHub App is on the roadmap for org-wide install but not built today.
Will labels be set automatically?
Yes — Screendog auto-applies a single label per recording type (bug → `bug`, incident → `incident`, doc → `documentation`, demo → `sales`, pr → `code-review`) and a severity label when one is set. The labels are sent in the `POST /repos/:owner/:repo/issues` payload; you can add or remove labels in GitHub afterwards.
Try Screendog free.
5 recordings on the free trial. Real Linear, GitHub, Notion, Slack, and Jira filing. No credit card.
Start a workspace — free