2 ms·
Seriously. When I first looked this project had been pushed the first commit two hours prior. Projects should be at least 3 months old or automatically remove
by throwatdem12311 6mo ago
Seriously. When I first looked this project had been pushed the first commit two hours prior. Projects should be at least 3 months old or automatically removed.
- ulimn 6mo agoBut then that would have the downside of falsely blocking projects that were developed in private and then just pushed to Github (or any public repo). Like I always use my own, self-hosted Forgejo for everything by default.
- deleted 6mo ago[deleted]
- throwatdem12311 6mo agoIf you develop on your own private instance and then mirror to GitHub to release it then there will be 3 months of git history in the logs.
- sumeno 6mo agoIf it's a project you actually care about and are actively working on it'll be just as good 3 months from now. If it's something that'll be irrelevant in 3 months why should anyone care about it?
- ulimn 6mo agoThat is true in most cases I guess but just look at the current product in OP. In 3 months, at the pace AI products evolve, we might "all" be using the next AI coding harness and Claude Code could be a thing of the past. So it's not a long lasting tool like curl for example. All I'm trying to say that generalizing like suggested might exclude some useful things.
- deleted 6mo ago[deleted]
- KallDrexx 6mo agoFwiw git history can be forged pretty easily. You can re-timestamp commits