Re: [ISSUE] [CLOSED] [RFC] Stale issues/pulls action

[github-actions[bot] <github-actions[bot]@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 2181 bytes --]

Closed issue by dmarto on void-packages repository

https://github.com/void-linux/void-packages/issues/36657

Description:
Related to: #36253 #36399 #36462

My believe is that with the current action and settings, the backlog won't disappear.

The action tries to consume all open issues and PRs, on every run. 
Even with the max hourly limit of 1000 operation, the action can't check and label all currently open items.
(can be seen in the debug runs from @maldridge) 

As of now ~210 issues and ~418 PRs are supposed to be **Stale**.
(taking into account the change from #36609, https://github.com/void-linux/void-packages/issues?q=is%3Aopen+updated%3A%3C%3D2022-01-11+no%3Aassignee+-label%3Arequest)

At the current rates of new new issues/PRs, I believe they will never be marked, only very few (the newest of the oldest) items will get marked.

Also there seems is another issue with the action - it doesn't count PR review comments as updates for the action, example #34884. That PR got marked Stale, received a review, and the next day the action saw the changes, but didn't count them as comments and left the Stale label. Thus it seems, only real comments are counted. 

---

I am suggesting to raise the operation limit to something like 400 (which should result in roughly 50-60, newly marked items per run), so there can be at least some progress. The other actions, are not doing many requests, so for the one random hour in the middle of the night this should be okay.

Multiple runs a day, can also be an option - but they will mark one or two new items, as currently the bulk of the operations is spent on fetching brand new items and checking current stale ones. 

Of course an option will be to find or write a smarter action
 - that can has better access pattern into the backlog (i.e not always starting from the newest issue/PR)
 - possibly even split itself into two actions that can run in different hours (issues and pulls)


P.S. There seems to be a v5 of the action, but it doesn't address any of the concerned topics.

P.P.S https://github.com/Sonia-corporation/stale may be a solution, but I haven't looked too much into it.