Did you check the docs?
Is your feature request related to a problem? Please describe.
Issues in this repo are being marked stale after 30 days of no activity. That is a bad idea for bug reports, because if you have a month or two where you don't have time to work on the project, the bug reports will disappear into the "closed" category and you won't remember that you haven't worked on them. But it's a terrible idea for feature requests, which end up either getting closed prematurely, or end up getting LOTS of "not-stale" spam that serves no purpose but to annoy everyone.
Case in point: #2111 (closed without anyone looking at it) and #2105 (closed without anyone looking at it, and reporter is asking for it to be reopened) and #2097 (closed without anyone looking at it) and #2041 (closed because the user who really wanted it open, and has been bumping it to prevent stalebot from closing it, didn't see the stalebot warning for just one week and now the issue is closed — and note that the user is asking for it to be reopened) and #2019 (which is a feature request! Feature requests should NEVER be considered stale! And notice that the user bumped it once, but forgot to bump it a second time).
Describe the solution you'd like
Get rid of stalebot in this and other nvim-related repos that you maintain. It's hurting the project: you end up with tons of feature requests that go unfulfilled, and tons of bug reports that never get fixed, because the stalebot closed them prematurely. Unless you were to go through all the closed issues and look for ones that need reopening (which is even more work than not having a stalebot in the first place!), they'll never get fixed/implemented.
Describe alternatives you've considered
Just don't use a stalebot. If issues stay open for six months before getting closed, that's not a big deal: it gives you a list of things that need working on, far more easily than having to dig through the closed issues to separate out the ones that were actually fixed from the ones that were stalebot-closed.
Or, if you MUST use a stalebot, then for goodness' sake configure it not to apply to issues marked with enhancement! Feature requests should NEVER be considered stale! If a feature request is truly out-of-date, it's not that hard to close it manually.
Additional context
Similar request here: folke/trouble.nvim#685
Did you check the docs?
Is your feature request related to a problem? Please describe.
Issues in this repo are being marked stale after 30 days of no activity. That is a bad idea for bug reports, because if you have a month or two where you don't have time to work on the project, the bug reports will disappear into the "closed" category and you won't remember that you haven't worked on them. But it's a terrible idea for feature requests, which end up either getting closed prematurely, or end up getting LOTS of "not-stale" spam that serves no purpose but to annoy everyone.
Case in point: #2111 (closed without anyone looking at it) and #2105 (closed without anyone looking at it, and reporter is asking for it to be reopened) and #2097 (closed without anyone looking at it) and #2041 (closed because the user who really wanted it open, and has been bumping it to prevent stalebot from closing it, didn't see the stalebot warning for just one week and now the issue is closed — and note that the user is asking for it to be reopened) and #2019 (which is a feature request! Feature requests should NEVER be considered stale! And notice that the user bumped it once, but forgot to bump it a second time).
Describe the solution you'd like
Get rid of stalebot in this and other nvim-related repos that you maintain. It's hurting the project: you end up with tons of feature requests that go unfulfilled, and tons of bug reports that never get fixed, because the stalebot closed them prematurely. Unless you were to go through all the closed issues and look for ones that need reopening (which is even more work than not having a stalebot in the first place!), they'll never get fixed/implemented.
Describe alternatives you've considered
Just don't use a stalebot. If issues stay open for six months before getting closed, that's not a big deal: it gives you a list of things that need working on, far more easily than having to dig through the closed issues to separate out the ones that were actually fixed from the ones that were stalebot-closed.
Or, if you MUST use a stalebot, then for goodness' sake configure it not to apply to issues marked with
enhancement! Feature requests should NEVER be considered stale! If a feature request is truly out-of-date, it's not that hard to close it manually.Additional context
Similar request here: folke/trouble.nvim#685