github workflow stale
threshold does not provide sufficient time for review of pull requests
#7572
Labels
stale
threshold does not provide sufficient time for review of pull requests
#7572
This issue is prompted by the automatic closure (twice) of PR #7297 as "stale" (pull request was filed 2022.02.21, auto-closed 2022.05.12, manually reopened 2022.05.12, then again auto-closed 2022.08.06).
Steps to reproduce
Expected behaviour
Threshold should be long enough for core developers to have enough to time to accept or otherwise comment on the feasibility or improvements needed to the PR.
Actual behaviour
If no response in 30 days, the issue is marked by the bot as stale. 5 days later, if there is no response, the PR is automatically closed. While it keeps the "pull request" list fairly clean, it has a few disadvantages:
Browser/system information
Not relevant
Additional details
I can think of a few potential approaches:
.github/workflows/stale.yaml
to allow core developers enough time to respond to pull requests.could be tagged as such so that such pull requests would not be automatically expired as
stale
.The text was updated successfully, but these errors were encountered: