Connecting GitHub

What you need

1. The owner and repository name (for example acme / api)
2. The base branch fixes should branch from — main unless you say otherwise
3. A fine-grained personal access token scoped to that one repository, with Contents: read and write, and Pull requests: read and write

Why write access at all

Reading code needs only read access. The write half exists for exactly one action: pushing a branch and opening a draft pull request carrying the fix. Nothing else in this product writes to your repository — no pushes to existing branches, no merges, no releases.

A draft pull request is the safest possible write. GitHub will not merge one, auto-merge ignores it, and most CI configurations still run against it — which is exactly what Noviqent DevOps needs, since it then polls that same CI result before reporting back to the ticket.

What the draft PR actually contains

The complete new content of every file the model touched — a real, testable change, not a diff description or a proposal document. An engineer reviews it the same way they'd review any other PR, and marks it ready for review once satisfied.

Set it up

1. Connectors → Add connector → GitHub
2. Enter the owner, repository, and base branch, and paste the token
3. Click Test connection — it shows the repository's full name and the permissions your token actually has