GitHub is a team integration, not a personal one. Open it from a team at app.xysq.ai: go to your team and open the Apps tab (
/teams/:teamId/apps).Who can connect it
Connecting, choosing repositories, and disconnecting are admin and owner actions. Any team member can see the connection status and recall what’s been synced, but only admins and owners manage the connection.Connect GitHub
- Open your team’s Apps tab and find the GitHub card.
- Click Connect. A new tab opens for GitHub’s OAuth consent screen. Sign in and approve access.
- The card flips from Pending to Connected.
| Status | Meaning |
|---|---|
| Not connected | No GitHub connection for this team yet. |
| Pending | OAuth started, waiting for consent. |
| Connected | Live and watching your selected repos. |
| Paused (quota) | The team’s daily event cap is reached; syncing resumes after reset. |
| Error | Something went wrong; reconnect to fix it. |
| Disconnected | The connection was revoked. |
Choose which repositories to watch
Once connected, the card lists the repositories the connected account can administer. Toggle on the ones this team should watch. Only activity on the watched repos is synced; everything else is ignored. You can change the watched set at any time. Adding a repo starts syncing its new activity; removing one stops it.What gets synced
Activity on a watched repo is folded into the team vault as it happens:- Pull requests - opened, closed, and merged
- PR reviews - approvals, change requests, and review summaries
- PR comments - issue-style comments on a PR
- PR review comments - inline comments on specific lines
- Commits - pushes to the repo’s branches
repo:<owner>/<name> plus a github:<event> tag (for example github:pr_review or github:commit). Events on the same pull request are folded together under one thread, so a PR’s discussion stays grouped rather than scattered.
Ask any connected agent, or xysq Chat, things like:
Activity logs
Every GitHub event xysq processes lands in the team’s activity logs. Open a team’s Logs tab (/teams/:teamId/logs) and switch to Apps to see what was kept, when, and from which repo.
Disconnect
Click Disconnect on the GitHub card (admin or owner only). New activity stops syncing. Memory already in the team vault stays and remains recallable. Reconnect later to pick up new activity again.Related
- Teams - team vaults, roles, and recall
- Integrations overview - how connectors work and how to read the logs