GitHub integration

GitHub metrics Swoop can read

Read-only, and only what you point it at.

• ✓Pull requests opened
• ✓Pull requests merged
• ✓Deployments started

History arrives on connect. GitHub hands over past values, so signals can appear on the first sync.

Goals from GitHub numbers

Swoop proposes each one with your own baseline in it. Nothing is asked of anyone until you accept.

What it asks, and who it asks

Phrased from the change, never from a theory about the cause — a leading question buys agreement instead of information.

Usually answered by: Engineering and Product Answering is free on every plan — you are never billed for the people who reply.

Connecting it

This one takes a little setup. A fine-grained token for the selected repository, with Pull requests and Deployments set to read-only. Deployment records count starts, not successful releases.

1. 01Repository

   One repository per connection. GitHub.com repositories only.

2. 02Fine-grained access token

   GitHub → Settings → Developer settings → Personal access tokens. Select this repository and grant Pull requests: Read and Deployments: Read. Your organization may need to approve it.

3. 03Deployment environmentoptional

   Optional. Leave blank to include every environment. Pull requests always cover the whole repository.

4. 04Choose what it may watch

   Every source states what it is allowed to look at. Ingesting everything available is how this becomes another dashboard nobody opens.

Credentials are encrypted and used read-only — nothing is ever written back to GitHub. Answers are synthesized by an open-weights model on Amazon Bedrock, so no foundation-model vendor sees your data; Enterprise runs that model in your own AWS account.

Other integrations