The Code pages count the BlockoutGames GitHub organization's work from the latest GitHub snapshot, which the collector takes every 30 minutes. Each page says when it was collected ("Collected 12 minutes ago"). Nothing asks GitHub when a page opens.
Code numbers at a glance
- Commitscommits
Window: GitHub weeks (Sunday 00:00 UTC) in the range. Source: GitHub's contributor statistics, or merged pull requests when those are empty ("Estimated").
- Pull requests opened, mergedpull requests
Window: created or merged in the week or range, by author.
- Cycle timehours, median
Window: pull requests merged in the week or range. Null: none merged.
- Time to first reviewhours, median
Window: pull requests first reviewed in the week or range. Null: none reviewed.
- Reviewedpull requests
Window: reviews a person submitted in the range.
- Waitingtime
Window: now, since review was first asked of a reviewer still asked.
- Lines changedlines
Window: merged pull requests, by merge date.
- Days between releasesdays, median
Window: all recorded history, per repository. Null: one release or none.
The formulas, written out:
cycle time = merged_at - created_at (merged pull requests only)
time to first review = first submitted review by someone else - created_at
lines changed = additions + deletions (merged pull requests, by merge date)
release cadence = median days between a repository's consecutive published releasesRanges and weeks on the Code pages
The weekly charts use ranges of 30 days, 90 days (the default), 1 year or all history; Members also has 7 days. Weeks are GitHub's contribution weeks, starting Sunday 00:00 UTC, not the studio's Monday weeks. A week that overlaps the start of the range counts whole, so the totals agree with the charts.
Bots are left out
Accounts whose login ends in [bot] (dependabot, github-actions, renovate) are left out of every count, tile, ranking and chart: their pull requests are removed and their reviews dropped. The one exception is the Pull requests list, which has an Include bots box.
Commits
Commits to each repository's default branch, per week and per person, from GitHub's contributor statistics. GitHub often answers those empty or "still being computed" for this organization, and then every commit count comes from merged pull requests instead, never a mix: each merged pull request counts its commits in the week it merged, under its author and repository. A chart or tile using this says "Estimated from merged pull requests".
The estimate misses work pushed straight to a branch without a pull request, counts every commit of a squash-merged pull request though it lands one, and credits all commits to the pull request's author.
Pull requests opened
Pull requests created in the week or range, by their author.
Pull requests merged
Pull requests merged in the week or range, by their author. Throughput on the Code overview draws opened and merged per week.
Cycle time
The time from opening a pull request to merging it, in hours. Median cycle time is the median over the pull requests merged in the week or range; per person, over their merged pull requests. Pull requests that were closed without merging, or are still open, are not in it.
Time to first review (review turnaround)
The time from opening a pull request to its first submitted review by someone other than its author, in hours. Pending review drafts do not count. Median time to a first review on Reviews is the median over the pull requests first reviewed in the week or range.
Reviews (pull requests reviewed)
A person's reviewed count is how many pull requests they submitted a review on (any review but a pending draft) during the range, on the Members page and a member's page.
Waiting for review (the review queue)
A pull request is waiting for review when it is open, not a draft, and either has reviewers asked, or none of the latest reviews on its newest commit approves it or asks for changes (comments alone do not count). The queue is ordered by how long each has waited, oldest first.
Waiting is the time since review was first asked of a reviewer still asked (from the pull request's timeline; marking it ready for review starts over). The oldest wait is the longest of those. The Code overview's waiting tile also says how many wait on your own GitHub login.
Lines changed
Every line count in the Code section is the lines added plus the lines removed that GitHub reports for merged pull requests, by merge date. Work pushed without a pull request is not counted. Lines per merged pull request and a person's median size are the median of added plus removed over their merged pull requests.
Pull request sizes
The size bands on the Pull requests page are 0 to 10, 11 to 50, 51 to 200, 201 to 500, 501 to 1,000 and over 1,000 lines changed. Open pull requests by age groups every open one, drafts included, by the time since it was opened.
Releases
Releases published in the week or range; drafts are not counted. Repositories releasing is how many repositories published at least one.
Days between releases (release cadence)
For each repository, the median number of days between its consecutive published releases, over all recorded history. A repository with one release has none. The organization's median is shown on Releases.
Open pull requests and stars over time
Drawn from the daily history of snapshots (the last snapshot of each UTC day), so they start on the day collection began. Until there are enough days the chart says the history is too short.
Two-factor status
Owners see how many members have GitHub two-factor authentication on; members see none. If GitHub does not report it, the panel shows "not reported".
Related: Code, Code overview, Pull requests, Reviews, Members, Collector and freshness, Glossary.
Updated