GitHub App integration

Bugmole's dashboard can link a QA finding — a UI parity issue or a piece of TestFlight feedback — to a real GitHub issue, so the finding has an anchor to the fix. Once linked, the issue's open/closed state syncs back automatically.

What it does

• Link a finding to an existing GitHub issue, or create a new one directly from the dashboard.
• Search issues in the connected repository from the same panel.
• Sync state automatically: when a linked issue is closed or reopened on GitHub, the dashboard reflects it within seconds — no manual refresh needed.
• Works from both the Parity bugs panel and the TestFlight feedback panel, and lists every linked issue in one place under Linked issues.

Support for other trackers (Jira, Azure DevOps, GitLab) is planned behind the same linking model.

How it works

Bugmole connects to GitHub as an installable GitHub App, not a personal access token. This means:

• Access is scoped to the specific repositories you choose to install it on.
• Each Bugmole project connects independently — installing on one repository does not expose others.
• No long-lived credential is stored per project.

Connecting a project

1. Open a project's Linked issues panel in the dashboard.
2. Click Connect GitHub.
3. Choose the GitHub organization and repositories to install the app on.
4. You're redirected back to the dashboard once GitHub confirms the installation.

If your org requires admin approval for app installations, the request is queued in GitHub until an admin approves it there — the connection cannot complete until you install a second time as an approved installer.

Limitations

• A project assumes a single GitHub App installation. If more than one is connected, the dashboard shows an explicit notice rather than guessing which to use.
• GitHub's Search API is rate-limited for Apps (30 requests/minute), so issue search is debounced client-side.
• Unlinking a finding only removes the link — it never closes, comments on, or otherwise modifies the GitHub issue itself.