6 ms·
I can't find any reason why I would have made it public. I made the repo in 2014 for internal use and don't like to share projects like that. I'm pretty careful
by johncoatesdev 2y ago
I can't find any reason why I would have made it public. I made the repo in 2014 for internal use and don't like to share projects like that. I'm pretty careful when releasing any code publicly. It's some code that other private projects depend on. I searched for any references in public code and there are none, so there should have been no reason to make it public.
Interestingly my public code with thousands of stars isn't in "The Stack".
- bredren 2y agoThis shouldn't be something where we're relying on recollection. Presumably github repo privacy state has an audit trail. This would allow GH to prove / disprove claims on any given repo easily. I hope a rep steps in to do so.
- johncoatesdev 2y agoYeah I agree. Tried https://news.ycombinator.com/item?id=39771541 https://news.ycombinator.com/item?id=39771541 but there's nothing related to this repo. Does GitHub send an email out when you make something public? I don't have any emails related to this repo.
- simonw 2y agoI just upgraded the tool at https://observablehq.com/@simonw/github-public-repo-history https://observablehq.com/@simonw/github-public-repo-history to use lowercase comparisons (previously it was case sensitive) so it's worth having another look.