Connect GitHub to OverlayQA
Last updated: October 15, 2026
Connecting GitHub to OverlayQA lets you file design QA issues as GitHub Issues in the repositories you choose. Each issue carries the OverlayQA title and a Markdown body with the page URL, element selector, computed CSS values, severity, browser and viewport, with screenshots embedded as images. Closing or reopening the issue in GitHub closes or reopens it in OverlayQA.
Connect GitHub and Install the App
- Open Integrations in the OverlayQA dashboard and connect GitHub. A GitHub authorization page opens; approve access for OverlayQA.
- Install the OverlayQA GitHub App on the account or organization that owns your repositories, and choose which repositories it may open issues in.
- Back in OverlayQA, the GitHub card shows as connected.
Tip: OverlayQA can only file issues in repositories the app is installed on with permission to write issues. To add a repository later, change the app installation in GitHub and refresh the repository list in OverlayQA.
Choose a Repository
Every export asks for the repository. The picker lists the repositories the app is installed on that have Issues enabled and are not archived, private and public alike.
Export Issues
- Open an issue and choose Export from its actions menu, or select several issues and export them with bulk actions.
- Choose GitHub as the destination and pick the repository.
- Confirm. OverlayQA opens one GitHub issue per OverlayQA issue.
Exports work on the dashboard and in Team Review. Bulk actions handle up to 100 issues at a time.
What Gets Exported
| Field | Description |
|---|---|
| Title | The issue title from OverlayQA. |
| Body | Markdown with the issue description, the screenshots embedded as images, page URL, Figma frame link when there is one, type, severity, browser, viewport, element tag and CSS selector, computed CSS values, AI analysis, the comments present at export time, and a link back to the OverlayQA issue. |
What Is Not Exported
Note: There is no field picker for GitHub: issues are opened without labels, assignees or a milestone, and you set those in GitHub. GitHub Issues has no file attachment API, so screenshots are image links in the body rather than uploaded files. CSS values are the computed values from the live page, not the expected values from a Figma design.
After Exporting
The issue shows a Synced to card naming GitHub, with a link to the GitHub issue.
Two-Way Status Sync
OverlayQA listens to the GitHub issues webhook event for the repositories the app is installed on. Two actions change the OverlayQA issue:
| In GitHub | In OverlayQA |
|---|---|
| Issue closed | Issue closed |
| Issue reopened | Issue reopened |
Note: Only status syncs. Comments, labels and assignees do not sync in either direction, and pull request events are ignored, so this is a two-way status sync rather than a full mirror of the issue.