Code integration

GitHub and Pacia

GitHub is the fullest integration Pacia has. Install the app on the repositories you choose and pull request events arrive in real time; or paste a read-only token if you would rather not install anything.

What Pacia reads from GitHub

  • Pull requests, reviews, review comments and merge events

  • Repository metadata and branch information

  • Organisation membership, for mapping people to teams

  • Push events and check runs, for deployment and failure signals

Connecting it

  1. Sign in with GitHub 1 min

    Your first sign-in creates your Pacia organisation automatically. There is no separate account-creation step.

  2. Choose your connection 2 min

    Install the Pacia GitHub App on selected repositories for live webhooks, or use Connect via Access Token with a read-scoped personal access token. The app can be installed by anyone with admin rights on those specific repositories — you do not need an org owner.

  3. Let the backfill run ~15 min

    Up to 180 days of pull request history pages through per repository. You can carry on setting up teams while it runs.

Limits, stated up front

Every integration page on this site lists what the integration does not do. Finding that out during a trial is worse for both of us than finding it out now.

  • Pacia reads pull request metadata, not file contents, and never analyses your source code.

  • App permissions requested are Pull requests (read), Metadata (read) and Members (read) — nothing writable.

  • Repositories connected by token have no live webhooks; they reconcile every 20 minutes or on demand.

Connect GitHub and see your own data