GitHub merged pull requests
The organization's repositories, and the pull requests closed in each during the window: the number, when it merged or closed, and nothing else. Never a diff, never a comment, never a file.
Access
- Kind
- A read-only key you paste
- What to give
- Fine-grained token, pull requests read
- Why that one
- A token that can read pull requests and repository metadata, and nothing else. This source writes no spend: it reports what the spend produced.
What it attributes on its own
- From the source
- merged pull requests per day · pull requests closed without merging, so the rate is visible · the repository each belongs to
- Needs a rule or a trace
- which pull requests an assistant helped with — GitHub records no such thing, so cost per merged pull request is a floor on the cost per assisted one · the workflow, which you tell us: a repository's name does not say which workflow its pull requests belong to · how large or how good a pull request was
The addresses it calls
- https://api.github.com/orgs/
- https://api.github.com/repos/
Only these. A call anywhere else is refused before it leaves, and every call is logged.
Connecting it
- Create a fine-grained token. Owned by the organization, with two read permissions and no write. Open ↗
- Name the workflow these count for. The workflow your coding assistants serve. Its spend divided by these merges is your cost per merged pull request.
- Paste both and click Test and connect. Valistry reads the last seven days of closed pull requests, reports how many merged, then fills thirty.
Not every merged pull request had help, and GitHub cannot tell us which did. Where your assistants write a trace id into the branch or the commit, we can join exactly instead of by workflow; ask us and we will read it.