Integrations · GitHub

Connect GitHub

OMG QA connects to GitHub through a GitHub App. Your team connects in one click — no personal access tokens, no manual webhooks. Once connected, findings link to pull requests, a finding moves to Ready for retest when its fixing PR merges, and you can open a GitHub issue straight from a finding.

🔌 Connect GitHub → ✅ Install on your repos → 🔗 Findings ↔ PRs, automatically

For your team — connect in one click

Open Integrations

In OMG QA, go to Settings → Integrations and click Connect GitHub. (You need the Manage projects permission.)

Install on your repositories

You're sent to GitHub's “Install OMG QA” screen. Pick the repositories you want (or All repositories) and click Install. That's the only choice you make — GitHub handles the rest.

Done

GitHub sends you back to OMG QA, already connected. No token to paste, no webhook to set up. You can disconnect anytime (it just uninstalls the app from your repos).

Why it's safe. OMG QA never sees a password or a long-lived token. The GitHub App is granted only the permissions it needs (open issues, read pull requests), scoped to the repositories you choose, and OMG QA uses short-lived per-install tokens that GitHub rotates automatically.

One-time setup — register the “OMG QA” GitHub App

This is done once, by your OMG QA administrator (self-hosted or your own deployment). After it's registered, every workspace connects with the one-click flow above — they never touch any of this.

Create the GitHub App

On GitHub, go to Settings → Developer settings → GitHub Apps → New GitHub App (for an org, use Organization settings → Developer settings). Fill in:

App name: OMG QA (must be unique on GitHub — e.g. OMG QA Quality).
Homepage URL: https://omgqa.com
Callback / Setup URL: https://api.omgqa.com/api/v1/integrations/github/setup — tick “Redirect on update”.
Where can this be installed: Any account (so your customers can install it).

Set the webhook

Turn the webhook on and set:

Webhook URL: https://api.omgqa.com/api/v1/integrations/github/app/webhook
Webhook secret: a long random string — generate one and keep it, you'll paste it into config in step 4. (e.g. openssl rand -hex 32)

Permissions & events

Repository permissions:

Issues — Read & write Pull requests — Read-only Contents — Read-only Metadata — Read-only

Subscribe to events:

Pull requestPush InstallationInstallation repositories

Click Create GitHub App.

Copy the credentials into OMG QA

On the new app's page, note the App ID and Client ID, copy the app slug from its public URL (github.com/apps/your-app-slug), and click Generate a private key to download the .pem. Then set these in your OMG QA configuration (user-secrets, environment, or appsettings):

// Integrations → GitHub App (vendor, one-time) Integrations:GitHubApp:AppId = "123456" Integrations:GitHubApp:AppSlug = "omg-qa-quality" Integrations:GitHubApp:ClientId = "Iv1.abc123..." Integrations:GitHubApp:WebhookSecret = "<the secret from step 2>" Integrations:GitHubApp:PrivateKeyPem = "-----BEGIN RSA PRIVATE KEY-----\n...\n-----END..."

Restart OMG QA. Connect GitHub now appears in every workspace's Integrations.

Register once, click once. That's the whole trade: you set up the GitHub App a single time, and from then on every customer connects their own repos in one click — no tokens, no per-repo webhooks, ever.

What you get once it's connected

🔗 Findings ↔ PRs

Link a pull request to a finding (or let an agent do it). The finding shows the PR's live state.

✅ Retest on merge

When the fixing PR merges, the linked finding moves to Ready for retest — no manual status change.

🐛 Open an issue from a finding

File a GitHub issue straight from a finding, in the repo you choose — using the installation's own token.

Prefer Jira, Slack, GitLab or Azure DevOps? They connect the same one-click way — see Documentation. Driving findings from an AI agent instead? See the MCP guide.