Integration

GitHub Issues Integration for Design QA

Export UI bug reports from any live page into GitHub Issues with the screenshot, CSS selector, computed values and viewport data a developer needs. Close the issue in GitHub and it closes in OverlayQA.

Issues that arrive ready to fix

A GitHub issue that says "the button looks off" costs a developer a reproduction before the fix can start. OverlayQA's GitHub integration opens the issue in the repository you choose with the issue title as the GitHub title and a Markdown body that carries the page URL, the element's selector, its computed CSS values, the severity, and the browser and viewport it was seen in. Screenshots are embedded in the body as images, so the evidence sits next to the description instead of in a chat thread.

Issues can come from a click on the live page, from a client comment on a review link, or from a scan that found them: Auto Review, the accessibility audit and the design-token checks all produce issues with the same structure, so a contrast failure and a misaligned button are filed the same way. Export one issue from its actions menu or up to 100 at once with bulk actions, on the dashboard or in Team Review. Designers and clients report from the page without a GitHub account.

OverlayQA connects through a GitHub App you install on the repositories you choose, so it can only open issues where you allowed it, and only repositories with Issues enabled appear in the export picker. After export, closing the issue in GitHub closes it in OverlayQA and reopening it reopens it. Comments, labels and assignees stay in GitHub; this is a two-way status sync, not a full mirror.

How the GitHub integration supports development teams

• Full context in every issue: selector, computed CSS values, severity, browser, viewport and screenshots travel with the issue, so nobody reproduces the bug before fixing it.
• Filed in the right repository: pick the repository at export, from the ones the OverlayQA GitHub App is installed on.
• Found and captured issues alike: issues from Auto Review, the accessibility audit and design-token checks are filed with the same structure as a captured bug.
• Status that stays true: a GitHub webhook reports closed and reopened events back, so the QA list and the repository agree about what is fixed.

Frequently Asked Questions

Which design QA tools create GitHub Issues?

BugHerd, Marker.io and Userback each offer a GitHub integration that turns website feedback into GitHub Issues, and OverlayQA does too. OverlayQA adds detection: Auto Review, an accessibility audit and design-token checks find issues nobody reported, and every issue, found or captured, is filed with the element selector, computed CSS values and a screenshot. Designers and clients can report from the live page without a GitHub account.

How do I export an issue from OverlayQA to GitHub?

Connect GitHub from the Integrations page in the OverlayQA dashboard, then install the OverlayQA GitHub App on the repositories you want to file issues in. Open any issue in OverlayQA, choose Export, pick the repository and confirm. Bulk actions export up to 100 issues at once, on the dashboard or in Team Review. Only repositories with Issues enabled appear. The issue body is Markdown with the page URL, element selector, computed CSS values, severity and browser details, with screenshots embedded as images.

Does closing an issue in GitHub update OverlayQA?

Yes. OverlayQA listens to GitHub's issues webhook event, which fires with a closed or reopened action whenever an issue changes state. Closing the issue in GitHub closes it in OverlayQA, and reopening it reopens it. This is a two-way status sync: comments, assignees and labels do not sync in either direction, and pull requests are ignored.