← all organisations

coventry-city-council / People

15 human committers, 0 bots, and what the commit timestamps reveal about how GDS works.

Every commit carries an author name and email. Collapsing 26 per-repository author records by email gives 15 distinct identities - 15 people and 0 machines. Identity is keyed on email because it is the only stable key git offers; one person using both a work and a personal address will appear twice.

People

15
human committers
resolved by GitHub id, address or full name
0
automated identities
0% of all commits
13%
committed exactly once
2 people, one commit each
2
committed over 5+ years
the institutional memory

What stands out

The top 1% of committers wrote 39% of the human commits.

1 people out of 15 account for 432 commits. The top ten alone wrote 98%. This is the usual open-source power law, but it is worth noting in a government context: institutional knowledge is concentrated in very few hands.

13% of people committed exactly once.

2 of 15 committers made a single commit and never returned. 67% touched only one repository. A public organisation attracts drive-by contributors, and the numbers show GDS accepted them.

5.1% of commits land at the weekend.

Weekday work dominates, as you would expect from a civil-service delivery organisation with a strong stated position on sustainable pace. The residual weekend activity is concentrated in incident response and personal-time open-source work.

0% of all commits were made by machines.

0 commits come from 0 automated identities - overwhelmingly Dependabot. GOV.UK's documented policy is to auto-merge dependency upgrades where possible, and the commit history shows that policy working at scale.

0% of live repositories rest on a single person.

In 0 of the 1 live repositories with meaningful history, one individual wrote more than half of all commits. That is the ordinary shape of a large estate with many small tools, but it is worth knowing which ones - they are listed below.

Who writes the code

Top 25 committers by commit count

Humans only. Bots are charted separately below.

sichunlamsichunlam: 432432LamLam: 215215Coventry City CouncilCoventry City Council: 8383Viviana SagredoViviana Sagredo: 6969lekshmiremadevilekshmiremadevi: 6767cvbmc220cvbmc220: 5959holgatetomholgatetom: 5757HRowthornHRowthorn: 4646sichunlamsichunlam: 3232RukzanaRukzana: 2222MullardmanMullardman: 1111lukaszmilton10lukaszmilton10: 77JatinderCCCJatinderCCC: 66justanewonejustanewone: 11shivaanginishivaangini: 11

Who they work for

Committers by email domain

A rough proxy for employment. GDS staff use gov.uk addresses; GitHub's privacy setting hides the rest, and a long tail commit from personal accounts.

GitHub private emailGitHub private email: 1313gov.uk addressgov.uk address: 11Personal email (gmail etc)Personal email (gmail etc): 11

Churn and tenure

Distinct people committing each year

Counting anyone whose active span covers that year. The shape tracks GDS headcount and the delivery peaks of the mid-2010s.

96.84.52.2017: 21718: 21819: 41920: 92021: 62122: 72223: 42324: 52425: 325

How long people stay

Span from first to last commit anywhere in the org.

43210same day: 2same day< 1 mth: 1< 1 mth1-3 mth: 11-3 mth3-12 mth: 43-12 mth1-2 yr: 31-2 yr2-4 yr: 22-4 yr4-7 yr: 14-7 yr7 yr +: 17 yr +

When the work happens

Commits by hour of day

Author local time as recorded in the commit. A clean single-peak working day.

143107.271.535.8000: 150001: 702: 30203: 004: 00405: 006: 00607: 208: 190809: 7010: 811011: 10212: 1201213: 7414: 1041415: 13216: 1431617: 8818: 461819: 2820: 162021: 2022: 152223: 23

Commits by day of week

245183.8122.561.20Sun: 26SunMon: 163MonTue: 197TueWed: 245WedThu: 238ThuFri: 208FriSat: 31Sat

Reading the pattern

Weekend commits account for 5.1% of all activity. The working day peaks between 10:00 and 16:00 with a visible lunch dip, and tails off sharply after 18:00 - the signature of an organisation that does not run on overtime.

Concentration of knowledge

For each live repository with more than fifty human commits, how many people it takes to account for over half of them. One is a genuine key-person risk; four or more is a healthily shared codebase. 1 repositories qualify for the measure.

Bus factor across live repositories

Fewest contributors accounting for more than half the commits.

10.80.50.201 person: 01 person2 people: 02 people3 people: 13 people4 people: 04 people5 people: 05 people6 or more: 06 or more

Where a single person wrote most of it

Share of commits by the largest single contributor, for the most concentrated repositories.

The machines

Top automated committers

Dependabot dominates. GOV.UK runs an in-house govuk-dependabot-merger service that auto-merges qualifying upgrade PRs, which is why bot commit volume is so high.

Top 60 committers

CommitterEmail typeCommits ReposFirstLast Years
sichunlamgithub-private43232017-052025-078.2
Lamgov.uk21522017-052020-032.9
Coventry City Councilgithub-private8312022-122024-021.2
Viviana Sagredogithub-private6912022-062023-040.9
lekshmiremadevigithub-private6712020-042021-010.8
cvbmc220github-private5912021-022022-051.2
holgatetomgithub-private5722020-082025-125.4
HRowthorngithub-private4612020-112021-080.8
sichunlampersonal3232019-072021-102.3
Rukzanagithub-private2212024-012024-050.3
Mullardmangithub-private1112020-112020-120.0
lukaszmilton10github-private712020-062020-070.1
JatinderCCCgithub-private622024-032025-081.5
justanewonegithub-private112022-122022-120.0
shivaanginigithub-private112022-032022-030.0