Logo, head homehey
IntroductionFeaturesIntegrations

Overview

  • About Integrations

External - General

  • MCP Server
  • Raw File Export
  • Agent Skill Export

External - Tool Specific

  • Cursor Rules Export
  • Cursor Cloud Agents
  • GitHub

Internal Connectors

  • Mission Board Webhooks

Walkthroughs

  • Cursor
hey

Product Management for the
Vibe Coding Era

X

Legal

  • Terms
  • Privacy
  • Cookies
  • Imprint

Resources

  • Blog
  • Pricing
  • Signup
  • Login
  • llm.txt

Compare

  • Jira Alternative
  • Linear Alternative
  • Notion Alternative
  • Asana Alternative
  • Trello Alternative
  • Q for Vibe Coding

Integrations

  • Q + Cursor
  • Q + Claude
  • Q + Codex
  • Q + Windsurf
  • Q + VS Code
  • Q + v0
  • Q + Lovable
  • Q + bolt.new
  • Q + Replit

© 2026 Q. All rights reserved.

Made with ❤️ for builders by builders

GitHub Integration

Connecting GitHub to Q lets Q Product Manager comment on pull requests using product truth from your linked Q project. The integration works by connecting a GitHub account, granting repository access to the GitHub App, linking one repository to a project, and selecting which project pages and mission boards Q Product Manager can use as context.

Install the GitHub App

When installing the GitHub App, make sure the developer shown on GitHub is The-Nexus-Collective, the parent company behind heyQ.

GitHub App installation screen for Q Product Manager
Before granting access, confirm that the GitHub App developer is The-Nexus-Collective.

Setup

Connect a GitHub account

In Q, open the GitHub integration section and click Connect GitHub Account. This opens the GitHub App installation flow for Q Product Manager.

Grant repository access

On GitHub, choose which repositories the app can access. You can connect one or more repositories, and you can connect multiple GitHub accounts if needed.

Link a repository to the project

Back in Q, choose one connected repository and link it to the current project. The UI lets you pick from all repos available across your connected installations.

Choose accessible pages and boards

When linking the repository, select which standalone pages and mission boards Q Product Manager can access. Checked pages are used in PR truth context. Checked boards are also used for mission matching.

Adjust configuration later if needed

After linking, you can reopen the repository configuration and update the accessible pages at any time.

What Context Q Product Manager Uses

The linked repository stores a configuration containing accessiblePaths. These selected paths define what Q Product Manager can use when reviewing a pull request.

That includes:

  • Standalone project pages
  • Mission boards
  • Mission boards as matching signals for mission detection

If no pages are selected, Q Product Manager won’t have any project context for PR comments.

What Happens on a Pull Request

The PR workflow is implemented as a processing pipeline:

  1. fetchTruth loads the full linked product truth from Q
  2. matchMissions tries to match the PR to one or more missions
  3. searchRelevantContext finds targeted context relevant to the PR
  4. generateComment creates a structured truth-context comment
  5. postComment posts that comment back to GitHub

The end result is a pull request comment grounded in the selected Q context, rather than just the code diff alone.

Linked Repository Management

Once connected, Q shows:

  • Connected GitHub accounts
  • Linked repositories for the current project
  • The default branch for each linked repo
  • A summary of how many pages the repo link can access

From there, you can:

  • Link another repository
  • Reconfigure page access
  • Unlink a repository

Select the pages and boards that actually reflect product truth for that repository. Better source selection leads to better PR comments.

Result

After setup, Q Product Manager leaves a PR comment that covers truth context: the relevant project pages, missions, and targeted context needed to interpret the pull request against the product source of truth.

Example PR Comment

Here is an example of a Q Product Manager comment on a pull request for heyQ. In this case, the PR adds semantic search capabilities for Q Product Manager itself, and the comment connects that implementation back to the relevant product truth and mission context.

Example GitHub pull request comment from Q Product Manager
Example of a Q Product Manager PR comment showing relevant context, linked mission, and scope check.

GitHub integration also underpins some other workflows, such as repository-linked automation and Cloud Agent related flows, but the core setup starts with connecting an account, linking a repo, and selecting the right accessible paths.

Previous

Cursor Cloud Agents

Next

Mission Board Webhooks

On this page

  • Install the GitHub App
  • Setup
  • What Context Q Product Manager Uses
  • What Happens on a Pull Request
  • Linked Repository Management
  • Result
  • Example PR Comment