You stay in control. Pyloq only sees the repositories you pick, and anything it does on GitHub is clearly labelled pyloq[bot], so it's never mistaken for someone on your team.
Before you start
- Your code lives in a GitHub organization or personal account.
- You're an ownerof that organization. If you aren't, that's fine: you can send a request and an owner approves it.
- You're an Admin in your Pyloq workspace.
Setup instructions
1. Start in Pyloq
Open Pyloq, go to Connectors and click Connect on the GitHub card. GitHub opens and asks where to install Pyloq.
Always start from Pyloq. Installing straight from GitHub works, but Pyloq won't know which workspace it belongs to.
2. Choose your organization and repos
- Pick the organization your code lives in.
- Choose All repositories, or Only select repositories and tick the ones Pyloq should see.
- Click Install & Authorize. You're taken back to Pyloq, connected.
Not an owner? The button says Request instead. Your owner gets an email from GitHub; once they approve it, click Connect in Pyloq again to finish.
3. Pick what Pyloq tracks
- In Pyloq, click Add repository and choose the repos you want to follow.
- Set the branches you release from, for example your dev and production branches.
- Name branches after tickets (like
feature/PYL-123-login) so pull requests link to the right ticket. See GitHub branch naming.
What you get
- Smarter standups:Pyloq knows when a ticket's pull request has merged, so it asks the right question instead of “any update?”
- Reviews at a glance: see which pull requests are waiting for review, for how long, and which release they hold up. Nudge the reviewer in Slack with one click.
- CI problems explained: when a build fails or gets stuck, Pyloq tells you what broke in plain English.
- Releases:release notes, the Release Graph and what's live in production or staging.
- Team rules for AI coding tools: Pyloq opens a pull request that adds your team's conventions to
AGENTS.mdandCLAUDE.md, so Claude Code, Cursor and Codex follow them from the first prompt.
What Pyloq can access
GitHub shows you this list when you install. Here's what each one is for:
| Access | What Pyloq uses it for |
|---|---|
| Pull requests | Follow reviews and open pull requests, and open the team-rules pull request |
| Contents | Read releases, branches and READMEs, and add the AGENTS.md / CLAUDE.md files |
| Issues | Leave comments on pull requests |
| Webhooks | Get notified when a pull request is opened, reviewed or merged |
| Checks and commit statuses | See whether your builds and checks passed |
| Actions | Read build logs to explain what failed |
| Deployments | Show what’s live in production and staging |
Pyloq can'tchange your repository settings, read your secrets, edit your workflows or see your organization's members.
Change which repos Pyloq can see
On GitHub, go to your organization's Settings → GitHub Apps, click Configurenext to Pyloq, and add or remove repos. Keep any repo you track in Pyloq selected here, or Pyloq won't be able to read it.
Disconnect or uninstall
| If you… | What happens |
|---|---|
| Disconnect in Pyloq | GitHub is removed from that Pyloq workspace. The app stays installed on GitHub, in case other workspaces in your organization use it. |
| Uninstall on GitHub | Pyloq is removed from your whole organization (Settings → GitHub Apps → Pyloq → Uninstall), and loses access to all your repos. |