The Trends page (/code/trends, Trends in the Code rail) is the long view of the BlockoutGames organization's code: how much changes and how big each change is, how fast work flows, which days it happens on, and the open backlog and stars over time. Every signed-in member can read it.
The Trends page's range
The header switch offers 30 days, 90 days (the default), 1 year and all; every chart follows it. Weeks start on Sunday (UTC) and a week overlapping the range counts whole.
The Trends page's tiles
- Lines changedlines
The coral tile: lines added plus removed in pull requests merged in the range, with the added and removed split under it.
- Lines per merged pull requestlines
Lines changed divided by the pull requests merged, rounded, with how many merged.
- Median cycle timehours or days
The median from opening to merge for pull requests merged in the range.
- Open pull requestspull requests
Open pull requests in the latest daily snapshot, with the change over the range (such as +3 in the range). It needs stored daily history; until then it says No history yet.
Lines only count merged pull requests: work pushed straight to a branch is not in them. Definition: Lines changed.
Lines added and removed per week
Lines of the pull requests merged each week: added lines above zero, removed lines below, and the net in the readout.
Size of a merged pull request
The average lines changed per pull request merged that week. It needs merges in at least two weeks. A rising line means each change is getting bigger.
Cycle time and review turnaround on Trends
Two weekly medians: opening to merge, and opening to the first review by someone other than the author. Durations read in hours up to 72 hours and in days beyond.
Cumulative flow
Pull requests opened and merged, each added up from the range's first week. The gap between the two lines is work still open: a widening gap means more is opened than merged.
The weekly rhythm
Pull requests opened and merged, and reviews, added up by the UTC day of the week (Sunday first), so the busy and quiet days show.
When work lands
A calendar of pull requests merged per day: a row per weekday, a column per week, the last 53 weeks at most. Days after the latest collection are blank.
Commits by repository and by member on Trends
Two stacked weekly charts: Commits by repository (the seven busiest repositories, then the rest) and Commits by member (the seven largest contributors, then Everyone else). Bots are left out. When GitHub's statistics are missing, both say Estimated from merged pull requests; see Code.
Open pull requests and stars over time
Open pull requests over time (drafts included, bots left out) and Stars over time (across every repository, archived ones included) come from the last snapshot of each day. They are drawn once snapshots from two days in the range are stored; until then one line says so.
How fresh the Trends page is
The weekly charts read the latest GitHub snapshot, collected every 30 minutes; the two history charts read one stored snapshot per day. The header says Collected … ago. See Code.
The Trends page on a phone
Tiles sit two to a row and every chart takes the full width, one under another. From 1280 pixels the charts pair up two to a row, lines beside the merged size.
Every chart here can be put on your home page with Add to a page.
Updated