GitHub
Create GitHub issues from feedback, using a personal access token.
Pro and above. Setup is a token, an owner, and a repository.
Connect
Create a personal access token
GitHub → Settings → Developer settings → Personal access tokens.
- Fine-grained token (recommended): scope it to the one repository and grant Issues: Read and write.
- Classic token: grant the
reposcope. For a public-only repository,public_repois enough.
Copy the value — it's shown once.
Connect in Annot8
Integrations in the sidebar → GitHub → enter the token, the owner (the org or username) and the repository name → Connect, then Test.
For github.com/acme/storefront, owner is acme and repository is
storefront.
Enable it per project
Project → Integrations → toggle GitHub on.
Two ways issues get created
Automatically, for every new thread on a project where GitHub is enabled.
The issue is titled [Feedback] <comment> with the author, the comment, and a
link to the page in the body.
On demand, by right-clicking a thread and choosing Integrations → Create GitHub issue — which carries the full thread context: page path and URL, issue type, priority, status, expected and actual behaviour, and the element selector.
Enabling GitHub for a project files an issue for every piece of feedback. On a repository where issues are your actual backlog, leave it off and create issues on demand instead.
Permissions
The token acts as the account that created it, so issues show that account as the author. For a team setup, use a machine account rather than a person's token.
Different repositories per project
Set a per-project override with a different owner and repository under Project → Integrations.
Troubleshooting
401. The token was revoked, expired, or was pasted with whitespace. Fine-grained tokens expire by default — check the expiry date.
403 with a valid token. The token doesn't cover that repository. A fine-grained token has to list the repository explicitly, and for an organisation repo the org may need to approve the token.
404 on create. Wrong owner or repo, or issues are disabled on that repository. GitHub returns 404 rather than 403 for repositories a token can't see, so a 404 can also mean "no access".