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, commits and pull requests 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 that can install GitHub Apps on the organization or 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. You’ll be redirected to GitHub to install the Pilea GitHub App. Choose which repositories the app may access, and approve.
4. Back in Pilea, the integration’s settings open on Workspace Repository Access: “Choose which repositories AI can read for your workspace. This is read-only and only affects this workspace.”
5. Search and tick the repositories you want, then click Save workspace access.

Credentials are encrypted at rest, and you can disconnect anytime from the Advanced tab of the integration’s settings.

How repository access is scoped

• Read-only, always. Pilea reads repository content, commits and pull requests. It never writes to or modifies your code.
• Per workspace. The connection is organization-level, but each workspace picks its own set of repositories under Workspace Repository Access in the integration’s Settings tab. Granting a repo to one workspace doesn’t expose it to any other. Until a workspace selects at least one repository, Pilea reads nothing for it.
• Two layers of permission. A repository must be both granted to the Pilea GitHub App on GitHub and selected for the workspace in Pilea. Pilea will only let you select repositories the app can actually see.
• 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. Ask Pilea in chat where a reported bug likely lives, or let a skill reference the relevant module when it writes up a backlog item.

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

Troubleshooting

When Pilea can’t read a repository, it now tells you exactly why instead of a generic error. The messages you may see in chat or in a skill’s output, and what to do:

“GitHub is not connected for this organization” Connect GitHub Repositories from the Integrations page.

“GitHub is connected, but no repositories are selected for this workspace” Open the integration’s settings and select at least one repository under Workspace Repository Access.

“The repositories selected for this workspace are not accessible to the Pilea GitHub App” The repository was selected in Pilea but the app no longer has access to it on GitHub - usually because it was removed from the app’s installation. Grant the app access to it on GitHub, or select a different repository.

“GitHub sync is turned off for this workspace” Sync was disabled for this workspace. Re-enable it in the workspace integration settings.

“Could not reach GitHub” Usually transient. Retry in a moment.

A repository isn’t showing up in the multi-select Only repositories granted to the Pilea GitHub App appear. Add it to the app’s installation on GitHub, then reopen the settings.

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