How GitHub gave every repository a durable owner
ascertain
21 points
5 comments
July 09, 2026
Related Discussions
Found 5 related stories in 746.3ms across 14,015 title embeddings via pgvector HNSW
- An update on GitHub availability salkahfi · 346 pts · April 28, 2026 · 57% similar
- GitHub's take on age assurance for developers hanifbbz · 31 pts · May 20, 2026 · 52% similar
- GitHub is sinking herbertl · 220 pts · May 10, 2026 · 52% similar
- GitHub and the crime against software pplanu · 208 pts · June 01, 2026 · 52% similar
- Durable Execution the Hard Way abelanger · 12 pts · May 28, 2026 · 51% 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.