Close stale PRs after 60 days of inactivity

[Swiddis]

Description

Updates the stalled PRs action to close PRs that have been inactive for 60 days (marked "stalled" for 30 days). In general the stale PRs tend to not get addressed anyways, we currently have 14 PRs with no activity for 200 days. This is a logical followup to #3221, I want to make it a separate PR for dedicated discussion.

Note that closing PRs isn't a destructive action, authors can easily reopen them if they get falsely closed. It just keeps our pending list more tidy, and also encourages authors to push again for feedback if they believe their changes are relevant and aren't getting attention.

Related Issues

N/A

Check List

• New functionality includes testing.
• New functionality has been documented.
• New functionality has javadoc added.
• New functionality has a user manual doc added.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff.
• Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[RyanL1997]

Just being curious, was this not even enabled before? Why it was -1 here?

[anasalkouz]

I don't think we need to auto-close PR by default. Maintainers need to review stalled PR and take the proper action case by case.

[Swiddis]

I think it helps -- for the most part longstanding stale PRs fall into three categories that are all helped by this:

• Relevant, Pending author action: If the author has abandoned the PR, having an automated message and workflow communicates clearly what the next steps are, and removes workload from maintainers to play the guessing game of "Have they abandoned it long enough?". The alternative is to manually recreate this behavior which will be more inconsistent.
• Relevant, Pending maintainer action: Maintainers have a definite timeframe to work with and can't leave PRs sitting around, author knows they need to re-request maintainer action. Not having the action will make this slower/fuzzier.
• No longer applicable: less maintainer workload to have it auto-closed, forces maintainers to make decisions on PR applicability in the short-term to keep the review queue smaller.

[Swiddis]

Not planned after side-channel discussion