Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That's the actual insane problem.

I noticed long ago that unreferenced commits survive on GitHub for long, but I couldn't find a way to discover them.

I know that GitHub stores together the objects of many repositories, but they should have implemented and offered a way to gc them when they came up with that optimization.

Sure, there would still be the chance that someone already obtained the objects by the time you gc them, but it's a much lesser risk then leaving them there indefinitely (and they could provide a log of the last fetches to better assess the impact of the erroneous push).



> chance that someone already obtained the objects by the time you gc them

I was under the impression that there are various 'mirror github' projects that listen to the GitHub change event API and immediately crawl some/all commits.

If so, this isn't a chance - it is certain.


Ok, there's also the problem of accesses through the web interface, but it probably wouldn't take much to provide a short-lived log of them as well




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: