How GitHub gave every repository a durable owner
ascertain
21 points
5 comments
July 09, 2026
Related Discussions
Found 5 related stories in 144.0ms across 9,716 title embeddings via pgvector HNSW
- What does GitHub's security team even do? theorchid · 99 pts · July 26, 2026 · 53% similar
- GitHub Has an Availability Problem. Is It Time to Look Elsewhere? dhruv3006 · 63 pts · August 17, 2026 · 52% similar
- What's Wrong with GitHub signa11 · 20 pts · October 11, 2026 · 51% similar
- GitHub's new dashboard experience now the default vanyauhalin · 73 pts · October 03, 2026 · 51% similar
- Restructuring GitHub's bug bounty program soheilpro · 31 pts · July 23, 2026 · 49% similar
Discussion Highlights (1 comments)
simonw
A previous employer hit the problem where there were a ton of legacy features that didn't have clear owners and so it wasn't clear where to route bug reports. Their solution was to build a catalog of every feature and then assign EVERY one of them to an existing team. Teams might end up responsible for features that they had never seen before and had no knowledge of... but that was fine, because every other team was in the same situation. It worked great. Bugs got fixed. Teams figured it out.