Connect GitHub to measure what your coding agents ship, pull requests, issues, and how fast they merge.
What you can measure
- Count of Pull Requests, Issues, or Commits over a window.
- Average / sum / min / max Time to merge (hours) on PRs.
- Filter by repo, org, author, assignee, label, milestone, state, base branch.
Good things to measure: PRs merged per week, issues closed, time-to-merge trending down.
Connect it
In GitHub, nothing to set up. You authorize read-only access in the next step.
In Jents, Settings → Integrations → GitHub → Connect → authorize (scope: repo). Tip: add a repo or org filter on your metric so it counts only what you mean.
What Jents reads
Counts come from the Search API's total; time-to-merge is computed from PR timestamps (up to a 1,000-item sample). Never code, diffs, or file contents.
Specs
| Spec | Detail |
|---|---|
| Auth | OAuth (repo) |
| API | GitHub Search (REST 2022-11-28) |
| Access | Read-only, scoped |
| Reads | Count server-side; merge-time from timestamps |
| Refresh | Daily, plus on-demand |
Privacy & security
Read-only, counts and timestamps, never code or diffs. Every read goes through one audited, aggregate-only path and lands in your audit log. Credentials are encrypted at rest, we never train on or share your data, and you can disconnect anytime, see Privacy and Trust.