Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Nah, while ignored pull requests and tickets tend to rot a bit over time, that doesn't actually prevent you from directly going to the code. So in the worst case, you just drop all tickets and pull requests and continue from there.
But if you can spare a week for sifting through the tickets and filtering them for dupes and obvious bullshit (like feature requests), you can maybe profit from the bugs already being discovered.
And some of the neglected pull requests based on one of the last few commits may already ahve fixed some stuff. -
@Oktokolo
Dropping all issues & prs?
I think most people that were engaged or wanted to engage in your project would take this as a big 'fuck you' and turn their backs on you. -
Bring into the equation an amount of days since last merge (few PRs), just to be fair.
-
@vintprox Of course, though I don't think healthy projects should be able to boast with their 'impressive number' either way (∩โฺกโ∩)
Related Rants
Repositories with 1k+ issues and / or 50+ pull requests are basically lost causes I would think..
1. Hard to recover properly
2. The same people that let it come to that point won't be the ones to be able to recover it in the first place
'lost cause' as in the project will just slowly because worse and worse in most ways, not that it's outright useless / non-functioning / ..
Does anyone have a counter-example of such a project that did recover?
In regards to h3rp1d3v's rant
https://devrant.com/rants/5883807/...
rant
projects
issues