-
Notifications
You must be signed in to change notification settings - Fork 12.5k
63 lines (55 loc) 路 3.26 KB
/
Copy pathstale.yml
File metadata and controls
63 lines (55 loc) 路 3.26 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
name: 'Close stale issues and PRs'
on:
schedule:
- cron: '0 0 * * *' # Run daily at midnight UTC
workflow_dispatch: # Allow manual triggering
permissions:
actions: write
issues: write
pull-requests: write
jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@4391f3da665fdf50b6810c1a66712fb9ba21aa93 # v11.0.0
with:
# Days of inactivity before an issue or PR becomes stale
days-before-stale: 60
# Days of inactivity before a stale issue or PR is closed (after being marked stale)
days-before-close: 30
# Stale issue settings
stale-issue-message: >-
This issue has been automatically marked as stale because it has had no activity for 60 days.
It will be closed in 30 days unless there is a substantive update. If the problem still applies,
please provide updated context such as whether it is still reproducible, the affected version or
environment, its current impact, and any new reproduction details. A comment that only states that
the issue is "still relevant" does not give maintainers enough information to reconsider it.
close-issue-message: >-
This issue has been automatically closed after 90 days without activity. To request reconsideration,
please provide updated reproduction details, the currently affected version or environment, and the
present impact. Ask a maintainer to reopen this issue if it is fundamentally the same problem. If the
scope or reproduction has materially changed, create a new issue, link this one, and explain what has
changed.
stale-issue-label: 'stale'
# Stale PR settings
stale-pr-message: >-
This pull request has been automatically marked as stale because it has had no activity for 60 days.
It will be closed in 30 days unless there is a substantive update. If you intend to continue, please
describe the current status, address or acknowledge outstanding feedback, and confirm whether the
branch can be updated and the change remains ready for review. A comment that only states that the
pull request is "still relevant" does not provide enough context for maintainers.
close-pr-message: >-
This pull request has been automatically closed after 90 days without activity. To request
reconsideration, please explain why the change is still needed, confirm that the implementation is
current and ready for review, and address any outstanding feedback or conflicts. Ask a maintainer to
reopen this pull request if the existing branch and approach remain valid. Otherwise, create a new pull
request, link this one, and explain what has changed.
stale-pr-label: 'stale'
# Exempt issues and PRs with these labels from being marked as stale
exempt-issue-labels: 'pinned,security'
exempt-pr-labels: 'pinned,security'
# Only issues or PRs with all of these labels are checked
# Leave empty to check all issues and PRs
any-of-labels: ''
# Operations per run (helps avoid rate limits)
operations-per-run: 250