Home / Connectors / GitHub
Connector

GitHub connector: datasets and metric definitionsBeta

Bring in pull requests, reviews and default-branch commits for each developer: PRs merged, time to merge and to first review, reviews given, work type, areas of the code, and how much was AI-assisted. Updates daily.

3 datasets16 metric definitionsRead-onlyRefreshes daily

When you connect GitHub, Quiriz imports the datasets below and adds the metric definitions to Company Context, the one place your company’s definitions live. Every answer that uses one of these metrics uses the same definition, in the app, in Slack and in the Excel, Sheets, PowerPoint, Slides, Word and Docs add-ins. An admin can edit any of them.

DatasetsMetric definitionsQuestionsFAQ

Datasets

DatasetWhat it holds
[GitHub] Pull requestsOne row per pull request merged, opened or closed in the last 13 months (by merge date when merged, else creation date), across the connected repositories. owner is who gets credit (the merger when an AI agent opened it). Lines exclude lockfiles and generated files, and are a size, not a productivity score. AI-assisted counts only AI that marks its work (agent accounts, co-author trailers, tool footers), so it is a minimum. Promotion PRs (a long-lived branch merged into another, such as dev into main) are kept but left out of the metrics. Outside contributors and bots are labeled and left out of the metrics. When ranking developers, leave out anyone with fewer than 3 merged PRs in the period and break ties by PR count.
40 columnsrepo, pr_number, title, state, author, owner, developer_kind, author_association, team_member, is_promotion, head_branch, base_branch, created_at, merged_at, closed_at, date, month, merged, lines_added, lines_deleted, lines_changed, lines_added_raw, lines_deleted_raw, files_changed, size, work_type, work_type_source, area, top_folder, ai_label, ai_tool, ai_assisted, review_count, reviewed, hours_to_first_review, hours_to_merge, changes_requested, is_revert, reverted_later, commit_count
[GitHub] CommitsOne row per non-merge commit on each repository's default branch in the last 13 months. A commit from a pull request carries that PR's work type, area and owner; direct_push = 1 means it reached the default branch without a reviewed PR. Lines exclude lockfiles and generated files, and are a size, not a productivity score. AI-assisted counts only AI that marks its work (agent accounts, co-author trailers, tool footers), so it is a minimum. Promotion PRs (a long-lived branch merged into another, such as dev into main) are kept but left out of the metrics. Outside contributors and bots are labeled and left out of the metrics. When ranking developers, leave out anyone with fewer than 3 merged PRs in the period and break ties by PR count.
23 columnsrepo, sha, committed_at, date, month, developer, login, owner, developer_kind, team_member, pr_number, direct_push, lines_added, lines_deleted, lines_changed, files_changed, work_type, work_type_source, area, top_folder, ai_label, ai_tool, ai_assisted
[GitHub] ReviewsOne row per submitted review on a pull request in the Pull requests dataset; developer_kind and team_member describe the reviewer. Self-reviews and pending reviews are left out. Lines exclude lockfiles and generated files, and are a size, not a productivity score. AI-assisted counts only AI that marks its work (agent accounts, co-author trailers, tool footers), so it is a minimum. Promotion PRs (a long-lived branch merged into another, such as dev into main) are kept but left out of the metrics. Outside contributors and bots are labeled and left out of the metrics. When ranking developers, leave out anyone with fewer than 3 merged PRs in the period and break ties by PR count.
12 columnsrepo, pr_number, pr_author, reviewer, developer_kind, team_member, state, submitted_at, date, month, review, hours_after_open

Metric definitions

Each metric is a total over the period you ask about. A metric built from other metrics, such as a rate, divides the totals for the whole period; it does not average daily rates. Dated by is the date column that decides which period a row belongs to.

[GitHub] Pull requests

MetricHow it is calculatedDated byNotes
GitHub PRs mergedSum of merged, where state = 'merged' AND developer_kind <> 'bot' AND team_member = 1 AND is_promotion = 0merged_atPull requests merged, by merge date. Promotion PRs, bots and outside contributors are left out. When ranking developers, leave out anyone with fewer than 3 merged PRs in the period and break ties by PR count.
GitHub PRs openedCount of rows, where developer_kind <> 'bot' AND team_member = 1 AND is_promotion = 0created_atPull requests opened, by creation date, whatever happened to them since. When ranking developers, leave out anyone with fewer than 3 merged PRs in the period and break ties by PR count.
GitHub lines changedSum of lines_changed, where state = 'merged' AND developer_kind <> 'bot' AND team_member = 1 AND is_promotion = 0merged_atLines added plus deleted in merged PRs, lockfiles and generated files left out. A size, not a productivity score. When ranking developers, leave out anyone with fewer than 3 merged PRs in the period and break ties by PR count.
GitHub merge hoursSum of hours_to_merge, where state = 'merged' AND developer_kind <> 'bot' AND team_member = 1 AND is_promotion = 0merged_atTotal hours from opening to merging, over merged PRs. Use GitHub average hours to merge for a typical PR. When ranking developers, leave out anyone with fewer than 3 merged PRs in the period and break ties by PR count.
GitHub average hours to mergeGitHub merge hours ÷ GitHub PRs mergedmerged_atAverage hours from opening a PR to merging it. When ranking developers, leave out anyone with fewer than 3 merged PRs in the period and break ties by PR count.
GitHub reviewed PRsSum of reviewed, where developer_kind <> 'bot' AND team_member = 1 AND is_promotion = 0created_atPull requests that got at least one review from someone other than the author (bots left out), by creation date. When ranking developers, leave out anyone with fewer than 3 merged PRs in the period and break ties by PR count.
GitHub first review wait hoursSum of hours_to_first_review, where reviewed = 1 AND developer_kind <> 'bot' AND team_member = 1 AND is_promotion = 0created_atTotal hours PRs waited for their first review (from opening, or from leaving draft), over reviewed PRs. When ranking developers, leave out anyone with fewer than 3 merged PRs in the period and break ties by PR count.
GitHub average first review waitGitHub first review wait hours ÷ GitHub reviewed PRscreated_atAverage hours a PR waited for its first review. When ranking developers, leave out anyone with fewer than 3 merged PRs in the period and break ties by PR count.
GitHub PRs sent backSum of changes_requested, where state = 'merged' AND developer_kind <> 'bot' AND team_member = 1 AND is_promotion = 0merged_atMerged PRs that had at least one review asking for changes. When ranking developers, leave out anyone with fewer than 3 merged PRs in the period and break ties by PR count.
GitHub rework rateGitHub PRs sent back ÷ GitHub PRs mergedmerged_atShare of merged PRs that were sent back for changes, as a decimal (0.2 = 20%). When ranking developers, leave out anyone with fewer than 3 merged PRs in the period and break ties by PR count.
GitHub fix PRsSum of merged, where state = 'merged' AND work_type = 'fix' AND developer_kind <> 'bot' AND team_member = 1 AND is_promotion = 0merged_atMerged PRs whose work type is fix (from labels, the title prefix, or the AI labeler). When ranking developers, leave out anyone with fewer than 3 merged PRs in the period and break ties by PR count.
GitHub fix shareGitHub fix PRs ÷ GitHub PRs mergedmerged_atShare of merged PRs that were fixes, as a decimal. When ranking developers, leave out anyone with fewer than 3 merged PRs in the period and break ties by PR count.
GitHub AI assisted PRsSum of ai_assisted, where state = 'merged' AND developer_kind <> 'bot' AND team_member = 1 AND is_promotion = 0merged_atMerged PRs made by an AI agent or with an AI co-author marker. This is a minimum: only AI that marks its work is counted. When ranking developers, leave out anyone with fewer than 3 merged PRs in the period and break ties by PR count.
GitHub AI shareGitHub AI assisted PRs ÷ GitHub PRs mergedmerged_atShare of merged PRs that were AI-assisted, as a decimal. This is a minimum: only AI that marks its work is counted. When ranking developers, leave out anyone with fewer than 3 merged PRs in the period and break ties by PR count.

[GitHub] Commits

MetricHow it is calculatedDated byNotes
GitHub direct pushesSum of direct_push, where developer_kind <> 'bot' AND team_member = 1committed_atCommits that reached the default branch without a reviewed PR (pushed straight to it, or only through a promotion PR). When ranking developers, leave out anyone with fewer than 3 merged PRs in the period and break ties by PR count.

[GitHub] Reviews

MetricHow it is calculatedDated byNotes
GitHub reviews givenSum of review, where developer_kind <> 'bot' AND team_member = 1submitted_atReviews submitted, by the reviewer (approvals, change requests and comments); self-reviews left out. When ranking developers, leave out anyone with fewer than 3 merged PRs in the period and break ties by PR count.

Questions to ask

Ask GitHub in plain words

Try the questions on sample data with no signup, then connect GitHub read-only and ask your own.

Try Quiriz free →

Frequently asked questions

Does Quiriz change anything in GitHub?
No. The GitHub connector is read-only. Quiriz reads the data into datasets and never writes back to GitHub.
How often does the GitHub data refresh?
Once a day. Each dataset shows when it was last updated, and answers use the latest refresh.
Can I change how a metric is calculated?
Yes. The definitions are added to Company Context, where an admin can edit the formula, the filter or the date it uses. A daily refresh never overwrites a definition someone has changed.
Can I combine GitHub with other sources?
Yes. An admin can also define a metric from metrics on different datasets. See cross-source metrics.

All connectors: Quiriz connectors. Definitions on this page are generated from the product’s own connector code.