GitHub Issues and AI Pull Requests
Link a repository, turn feedback into GitHub issues, and on Pro have Claude or Copilot propose the fix.
An owner links one GitHub repository per project, and each teammate links their own GitHub account. Then any feedback item becomes a GitHub issue in one click, with the message, page, errors, screenshot and a Claude-written summary. On Pro, AI PR Fix has Claude open a pull request for an item with console errors, and Copilot Fix asks GitHub Copilot to.
GitHub issues work on every plan. The two AI fixes need Pro. For Linear or Jira instead, see Linear and Jira.
Connect a repository
Link your GitHub account
Open the project’s Settings and click the GitHub tab, then Connect GitHub. GitHub asks you to let Qaid reach your repositories. Approve it and you come back to the tab, which now reads “Connected as @” and your GitHub name, with Disconnect account beside it.
Pick the repository
Type in Search repositories… and click Connect beside the one you want. Private ones carry a Private badge. Only owners can do this; members see “Only the project owner can connect a repository.”
The tab then shows Repository Connected, the repository’s name, and who connected it and when. A project has one repository. Connecting another replaces it, and Disconnect (owners only) unlinks it after you confirm.
Linking GitHub here is not the same as signing in with GitHub. It is a second connection, used only for issues and fixes.
Link GitHub for each teammate
Qaid opens issues and pull requests as the person who clicks, using their own GitHub account. So every teammate who wants the buttons below opens the GitHub tab once and clicks Connect GitHub too. Until they do, the tab shows them that card even though the repository is linked, and their clicks fail with “GitHub not connected for your account”.
To unlink your own account, click Disconnect account beside “Connected as” and confirm. Qaid forgets your GitHub token, and the tab shows Connect GitHub again. The project’s repository stays linked, and issues already on GitHub are not touched. Members get the button as well as owners, since it is your own account.
Open a GitHub issue from feedback
Open an item and click Create GitHub Issue under Integrations. From the inbox, hover a row and click the GitHub icon. Either way the issue appears in the linked repository, and the button turns into Issue # and its number. Each item gets one issue.
What Qaid writes:
| Part | Content |
|---|---|
| Title | A priority and a title Claude wrote, such as [HIGH] Card payment fails at checkout. If Claude doesn’t answer, [MEDIUM] Feedback on and the page path |
| Labels | feedback, the item’s type (positive, negative, neutral or video), a severity, and priority: with the level |
| Body | The type, such as Positive 👍, then the page, the time, the message, the element’s selector and text, the console lines, a link to any recording, the screenshot, and a link back to the item |
| Comment | ”Claude’s Analysis”, with Claude’s guess at the cause |
The screenshot in an issue loads for a year. Anyone who can open the item in Qaid can still see it there after that.
Keep GitHub and the inbox in sync
When GitHub tells Qaid that an issue it opened was closed, Qaid archives the feedback and records when. If the person who closed it is on the project and has linked GitHub in Qaid, the archive names them too. Reopening the issue does not bring the item back.
Assigning the issue to someone on the project who has linked GitHub in Qaid assigns the item to them. A GitHub user who isn’t on the project is ignored. Unassigning the issue clears the owner.
That depends on GitHub sending issue events to Qaid, and nothing on the GitHub tab sets that up for your repository. If a closed issue leaves its item in the inbox, archive the item yourself.
Ask for an AI pull request
AI PR Fix and Copilot Fix are Pro. On Free their buttons don’t appear. Free vs Pro
AI PR Fix appears on items that came with console errors. Click it and the button shows its progress, from pending through analyzing and generating. When it finishes, it turns into AI PR # and a number, and the inbox row gets a PR # badge.
What Claude does, in order:
- Lists the source files on your default branch:
.ts,.tsx,.js,.jsx,.vue,.svelte,.css,.scss,.html,.jsonand.md, skippingnode_modules,distandbuild. - Reads the feedback and its errors, and picks the files most likely at fault.
- Reads up to five of them and writes the change.
- Commits it to a new branch,
fix/feedback-and the start of the item’s ID. - Opens a pull request against the default branch, links it back to the item, and asks you to review it.
Claude may decide it can’t fix the problem. The button then reads AI PR Fix Failed, and a message gives the reason; hover the button to read it again. Retry AI PR Fix beside it starts a fresh attempt. Nothing merges on its own: review the pull request like any other.
Hand it to Copilot
Copilot Fix appears once an item has a GitHub issue. Click it and Qaid posts a comment on that issue. The comment starts “@github-copilot Please analyze this feedback and create a fix:”, then lists the type, page, message, element and console errors, and asks for a branch and a pull request. The dashboard confirms with “Asked Copilot on issue #” and the number. Nothing opens in Qaid; follow the issue on GitHub.