Skip to content

Close inactive needs-info issues #9

Close inactive needs-info issues

Close inactive needs-info issues #9

# Keep the issue queue honest: once a maintainer marks an issue `needs-info`,
# the reporter has 30 days of inactivity to answer. We warn after 23 days and
# close 7 days later. Any new comment or edit resets the clock and removes the
# `closing-soon` label; maintainers remove `needs-info` once the answer is enough
# to resume triage.
name: Close inactive needs-info issues
on:
schedule:
- cron: "17 14 * * *"
workflow_dispatch:
permissions:
contents: read
issues: write
jobs:
stale:
if: github.repository == 'block/berd'
runs-on: ubuntu-latest
steps:
- uses: actions/stale@4391f3da665fdf50b6810c1a66712fb9ba21aa93 # v11.0.0
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
# Only issues deliberately blocked on the reporter. Never touch PRs or
# any other kind of issue.
only-issue-labels: needs-info
days-before-issue-stale: 23
days-before-issue-close: 7
days-before-pr-stale: -1
days-before-pr-close: -1
stale-issue-label: closing-soon
stale-issue-message: >-
🤖 We still need the information requested above to act on this issue.
It has been inactive for 23 days, so it will close automatically in
7 days if there is no reply. Add the missing details in a comment
and the countdown will reset. A maintainer will review the answer
and remove `needs-info` once the issue is actionable.
close-issue-message: >-
🤖 Closing because the information we need has not arrived after 30
days. If you can provide it later, leave a comment with the missing
details and a maintainer can reopen the issue.
close-issue-reason: not_planned
# A reply means the reporter is engaged. Keep `needs-info` until a
# maintainer confirms the answer is sufficient, but cancel the active
# close countdown immediately.
remove-issue-stale-when-updated: true