The Members page (/members, Members in the Code rail) shows the team person by person: what each member of the BlockoutGames GitHub organization opened, merged, reviewed and committed in the range. Every signed-in member can read it. The old address /people opens it. Membership itself is managed on GitHub, not here.
The Members page's range
The header switch offers 7 days (the default), 30 days, 90 days, 1 year and all. Pull requests and reviews count when they happened inside the range; commits count the whole weeks (Sunday, UTC) overlapping it.
The Members page's tiles
- Memberspeople
People in the organization in the latest snapshot, with how many are GitHub organization admins.
- Active in the rangepeople
The coral tile: members who opened, merged, reviewed or committed anything in the range.
- Pull requests mergedpull requests
Pull requests the members authored that merged in the range.
- Pull requests reviewedpull requests
Distinct pull requests each member reviewed, added up over the members (two people reviewing one pull request count twice).
The organization members table and its order
Organization members lists everyone, the most active first: activity is a person's pull requests opened, merged and reviewed plus their commits.
- Member
Picture, name and
@login(opens the member's page); Admin for organization admins.- Openedpull requests
Pull requests they opened in the range.
- Mergedpull requests
Their pull requests merged in the range.
- Reviewedpull requests
Distinct pull requests they reviewed in the range.
- Commitscommits
Default-branch commits in the range, or the estimate from merged pull requests.
- Lines mergedlines
Lines added and removed in their pull requests merged in the range.
- Median cyclehours or days
The median opening-to-merge time of those pull requests.
- Weekly
A sparkline of commits per week; pull requests opened per week for someone outside the seven largest committers.
A number GitHub could not give reads Unavailable. Bots are left out. Definitions: Code metrics.
Who sees two-factor status on Members
Only owners. Members see no two-factor status: the API leaves it out of their answer, since it says whose account is the easiest way in.
Under the table: how many members have two-factor authentication enabled, disabled or not reported, and Manage members on GitHub, which opens the organization's people page on GitHub. Each member's page also shows Two-factor on, Two-factor off or Two-factor not reported.
GitHub tells only an organization owner's credential who has two-factor turned off. When the collection's token or App may not ask, GitHub refuses (403), the run carries on, and every member reads not reported.
Merged by member and Commits per week
- Merged by member
A bar per person, pull requests they authored that merged in the range, with their median cycle time; a bar opens their page.
- Commits per week
Weekly commits stacked by person, the seven largest contributors named and the rest as Everyone else. Under the estimate it counts the commits of pull requests each person merged, by merge week.
Your access, at the foot of Members
The last line says your own access: Admin (an organization owner) or Member. Active members of the GitHub organization can sign in; organization owners are the studio's owners. See Roles.
Members before GitHub is collected
Before the first collection, the page lists Connected studio accounts instead: people who have signed in with GitHub before, with their access. It is not a live roster; membership is checked each time someone signs in.
How fresh the Members page is
It reads the latest GitHub snapshot, collected every 30 minutes; profiles (names and pictures) are refreshed once a day. See Code. Reading contribution numbers, folded at the foot, explains how commits and lines are counted.
The Members page on a phone
Tiles sit two to a row; the table scrolls sideways inside its card with each member's name held at the left edge; the two charts follow at full width.
Updated