Skip to content

Stale

Stale #20

Workflow file for this run

name: Stale
# Closes issues that have been waiting on the reporter for too long.
#
# The scope is deliberately narrow: `only-labels` means an issue is touched only
# while it carries `triage/needs-information`. Design proposals, feature requests
# and everything else in the backlog are never seen by this workflow, no matter
# how long they sit. Pull requests are excluded outright via the `-1` settings,
# so long-lived dependabot PRs are left alone.
#
# The label is a state bit meaning "waiting on the reporter". clear-needs-information.yaml
# removes it as soon as they answer, which takes the issue back out of scope here.
on:
schedule:
- cron: '30 1 * * *'
workflow_dispatch:
inputs:
dry-run:
description: 'List what would be marked or closed without changing anything'
type: boolean
default: false
permissions:
issues: write
jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v11
with:
only-labels: 'triage/needs-information'
days-before-issue-stale: 30
days-before-issue-close: 14
# Never touch pull requests.
days-before-pr-stale: -1
days-before-pr-close: -1
stale-issue-label: 'stale'
close-issue-reason: 'not_planned'
# Load-bearing rather than incidental: any activity drops the `stale`
# label and restarts the 30 day clock, which is what lets a maintainer
# ask a follow-up question without shortening the reporter's window.
remove-stale-when-updated: true
debug-only: ${{ inputs.dry-run || false }}
stale-issue-message: >
This issue has been waiting on additional information for 30 days and
will be closed in 14 days if nothing further arrives. If it is still
relevant, please add the requested details — that alone keeps it open.
A closed issue can be reopened at any time.
See
[docs/issue_lifecycle.md](https://github.com/zilliztech/milvus-backup/blob/main/docs/issue_lifecycle.md)
for how this works and what resets the timer.
close-issue-message: >
Closing because the information needed to investigate never arrived.
This is not a judgement about whether the problem is real. If it still
reproduces, please comment with the requested details and we will
reopen it.
See
[docs/issue_lifecycle.md](https://github.com/zilliztech/milvus-backup/blob/main/docs/issue_lifecycle.md)
for why this was closed and how to bring it back.