GitLab merged merge requests
Each merge request, except its content. Open and merge times, files changed and reviewers. Reverts, pipeline status and AI co-authors. Never titles, code, comments or commit messages.
Access
- Kind
- Sign in on the vendor's page; nothing typed here
- What to give
- Group and access token
- Why that one
- A group access token with read_api, or a personal one on GitLab.com Free. Valistry reads merged merge requests and adds no cost.
What it attributes on its own
- From the source
- merge requests merged per day, at the moment each merged; closed without merging, counted as unsuccessful; reverts, from GitLab's own revert title; an AI label, where your team sets one; who opened each, as a hash, and whether a bot or an agent did; files changed on each merged merge request; the AI tools named in its commits' Co-authored-by lines; comments, reviewers, who merged it as a hash, the pipeline's status and the time to merge; its own cost, where your tooling writes the trace id into the branch name
- Needs a rule or a trace
- which merge requests an assistant helped with, beyond the label, the agent that opened it and the co-author lines AI tools write: GitLab does not record it. The cost per assisted change is at least the cost per merged change; the workflow, which you tell us; lines added and removed: GitLab gives them only with the code, which is not read
The addresses it calls
- https://gitlab.com
Valistry calls only these addresses. It blocks any other call and logs every call.
Connecting it
- Create a group access token. Your group → Settings → Access tokens → Add new token Open ↗
On GitLab.com Free, make a personal access token with read_api instead: avatar → Edit profile → Access → Personal access tokens. Your tooling writes a trace id into the branch name? Write where it sits, under the trace id field, and each merge request gets its own cost.