July 9, 2026
Repo custody battle
How GitHub gave every repository a durable owner
GitHub cleaned house, slapped a name on every project, and commenters felt very seen
TLDR: GitHub forced every active internal project to have a clear owner and archived thousands of abandoned ones, ending the era of mystery code. Commenters immediately recognized the workplace drama: this can bring order, but it can also mean teams suddenly inherit baffling old projects they never wanted.
GitHub just did the corporate version of opening a junk drawer, dumping it on the floor, and demanding that every single item have a responsible adult attached. The company says it had more than 14,000 code projects floating around internally, with fewer than half clearly owned. In just 45 days, it tracked down owners for active projects, archived around 8,000 that seemed abandoned, and changed the rules so new projects can’t be created without naming who’s on the hook. In plain English: no more mystery projects sitting around like forgotten leftovers.
But the real juice is in the community reaction, where developers instantly turned this into a group therapy session about workplace chaos. Over in the comments, Simon Willison dropped the painfully relatable tale of a past employer solving a similar mess by assigning every feature to some team, whether they recognized it or not. That sparked the biggest unspoken hot take of all: is “ownership” a smart fix, or just a fancy way to dump random problems on unlucky teams? The vibe was half finally, some adult supervision, half congrats, you’ve invented organized blame.
And yes, there’s humor in the horror. The whole story taps into a universal office nightmare: that weird project nobody understands but everyone is suddenly responsible for when something breaks. The meme practically writes itself—“You touch it, you own it”—with a side of panic, resignation, and dark laughter from anyone who’s ever inherited a digital haunted house.
Key Points
- •GitHub says its primary internal organization had more than 14,000 repositories, with over 11,000 non-archived as of early 2025, and most lacked clear ownership.
- •The ownership gap caused operational and security problems, including difficulty routing secret scanning remediation work safely.
- •GitHub's prior ownership model relied on an internal Service Catalog that tracked deployed services, associated repositories, owning teams, executive sponsors, and maintainers.
- •That model worked from service to repository but did not reliably identify owners for repositories not tied to deployed services, such as docs, tools, and one-off projects.
- •GitHub says it validated owners for every active repository in about 45 days, archived around 8,000 inactive repositories, and made ownership mandatory when creating new repositories.