Connecting GitHub repositories

The GitHub Repositories integration gives Pilea’s AI read-only access to your code. When agents or analysis need technical context - how a feature is actually built, where the relevant code lives - they can read files from the repositories you’ve approved, on demand.

This is different from the GitHub Issues integration: repositories are about giving AI context, not about exporting backlog items.

What you’ll need

• Admin access in Pilea (only admins can change integration settings)
• A GitHub account with access to the repositories you want Pilea to read

How to connect

1. In Pilea, go to Integrations in the sidebar under Data Sources.
2. Find GitHub Repositories in the grid and click Connect.
3. Click Connect in the dialog and authorize access in GitHub.
4. After connecting, you’ll reach the Workspace Repository Access step: “Choose which repositories AI can read for your workspace. This is read-only and only affects this workspace.”
5. Use the searchable multi-select to pick the repositories, then confirm.

Credentials are encrypted at rest, and you can disconnect anytime.

How repository access is scoped

• Read-only, always. Pilea reads repository content and files. It never writes to or modifies your code.
• Per workspace. The connection is organization-level, but each workspace picks its own set of repositories in the Workspace Repository Access step. Granting a repo to one workspace doesn’t expose it to any other.
• On demand, not on a schedule. There’s no scheduled sync. Pilea reads code context only when an agent or analysis actually needs it.

💡 Tip: Only select the repositories that are relevant to the workspace’s product area. A tighter selection means the AI works from the code that actually matters.

Why connect repositories?

With code context available, Pilea’s agents and analysis can ground their work in how your product is really built - not just in what the feedback says. Connecting repositories is also one of the three steps in your activation checklist: as the in-app banner puts it, it “Activates Basil & Lily.”

ℹ️ Note: Repository access affects only the workspace it’s configured in. If a second workspace needs code context, configure its repository selection separately.

Troubleshooting

A repository isn’t showing up in the multi-select Check that the GitHub account or installation used to connect has access to that repository. If access was granted after connecting, disconnect and reconnect from the Integrations page.

I can’t change the repository selection Only admins can change integration settings. Ask a Pilea admin in your organization to update it.

Next: Exporting backlog items to GitHub Issues