Add close_issues.yml to GitHub workflows to close issues after extended period of inactivity #961
Conversation
|
@avaldebe current set up will mark stale after 1 year and close 14 days after. This is fairly lenient. I'm curious if you (and others @dulte @jgriesfeller ) think we should decrease this timeframe. Open to other suggestions - please mention here |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main-dev #961 +/- ##
============================================
- Coverage 78.95% 78.94% -0.01%
============================================
Files 105 105
Lines 18423 18421 -2
============================================
- Hits 14545 14543 -2
Misses 3878 3878
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
.github/workflows/close_issues.yml
Outdated
| days-before-issue-stale: 365 | ||
| days-before-issue-close: 14 | ||
| stale-issue-label: "stale" | ||
| stale-issue-message: "This issue is stale because it has been open for 365 days with no activity." |
There was a problem hiding this comment.
Could you add to the comment that the issue will close in x days. If it's not explicit, we will forget
There was a problem hiding this comment.
"This issue is stale because it has been open for 365 days with no activity. This issue will be closed in 14 days if not addressed."
Or something
There was a problem hiding this comment.
I worded slightly differently before I saw this comment but good suggestion.
lewisblake
changed the title
Close #960