&gt; Sounds like the only customers being lost were those using github for no-commit users. Is that really a huge segment? If so they just need a special account status to fix this.<p>I would think this is a large segment, or at least Github would like it to be. Any software company that sells its software directly, and so has a sales team, a support team, marketing and so on will need to make all of those people users in Github if they&#x27;re going to raise GH issues, see the code, prototype something for a client, help with branding, or anything else. If you&#x27;re using Github the way they want you to (issue tracking, wiki, all of the things Github adds over vanilla Git that are &quot;sticky&quot;&#x2F;hard to transfer to a competing service) you don&#x27;t want to restrict access to just your developers. You want your whole company to be using it.<p>In any software company I&#x27;ve worked for, those non-developer users number 3-4x the actual number of developers. And I&#x27;ve never worked for a company that would consider restricting which users could raise issues with the product.<p>I agree that having a non-commit account status that didn&#x27;t count toward the per-user pricing would fix this, for that particular (I think common?) case.