ci: close stale issues and PRs automatically #11778
Conversation
- Label all issues and PRs older than 1 year (except certain labels) as Stale, close if no further activity after warning period. - From this date forward, label issues with no activity for 30 days and still carrying the `Needs Triage` label as Stale, close if no further activity after warning period. - From this date forward, label PRs with no activity for 90 days as stale and close if no further activity after warning period. Issues and PRs with milestones or assignees are exempt.
Codecov Report
@@ Coverage Diff @@
## master #11778 +/- ##
=======================================
Coverage 69.01% 69.01%
=======================================
Files 312 312
Lines 16346 16346
Branches 4742 4742
=======================================
Hits 11281 11281
Misses 5037 5037
Partials 28 28 Continue to review full report at Codecov.
|
|
I have updated it to use a dry-run mode. Together with ACTIONS_RUNNER_DEBUG this could allow for some basic verification before it's thrown into the wild. |
There was a problem hiding this comment.
Hey @sigveio! Sorry I dropped the ball on this.
I think this is something we want to - 1.5k open issues iss too many to reasonably be able to address. I've had some extra time in the last couple of weeks, but I've only reduced the PR count by about 40 , and not even looked at issues unless linked to PRs. Being able to close out old ones, and then having new ones opened which follow the great templates you put together seems reasonable to me.
| days-before-pr-stale: 365 | ||
| days-before-issue-close: 5 | ||
| days-before-pr-close: 14 | ||
| exempt-issue-labels: 'Confirmed,Discussion,Documentation :book:,good first issue,Help Wanted' |
| with: | ||
| stale-issue-message: 'This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 5 days.' | ||
| stale-pr-message: 'This PR is stale because it has been open 1 year with no activity. Remove stale label or comment or this will be closed in 10 days.' | ||
| close-issue-message: 'This issue was closed because it has been stalled for 5 days with no activity.' |
There was a problem hiding this comment.
should we have something about "open up a new issue following the template and link to this issue if still relevant" thing?
|
Created the |
We should |
|
I tweaked this
I should also probably make a pinned issue explaining why we're doing and a place for people to provide feedback |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
This PR proposes two new jobs for the GitHub automated workflow.
They are based on the Close Stale Issues Github Action.
Details
Base conditions for all jobs:
Stalewill be closed with no further activity afterJob:
"Close stale issues and PRs older than 12 months"Legacy cleanup to label all* issues and PRs with no activity for 1 year as
Stale.*Click to see exemptions!
These are exempt:Impact 馃挜
This could potentially close almost 600 issues at this point in time.
It would also affect around 65 stale PRs.
Job:
"Close stale issues and PRs"Normal routine applying to all* new issues and PRs from this date forward.
Labels issues and PRs matching the following conditions as
Stale:Needs Triagelabel.These are exempt:
Motivation
Trimming down the amount of open issues and PRs could help make it easier to maintain an overview for those managing the project. I think it would also help make the project more approachable for potential contributors.
The new automated workflow would help take care of it going forward. 馃 馃挋
Things to consider / discuss
Todo before this could be merged:
StalelabelDocumentationlabel, as I'm not 100% sure if the bot plays well with it.Warning