Skip to content

Commit 1000d7e

Browse files
authored
Update stalebot settings (project-chip#36097)
Do not close PRs nor Issues Make the stale threshold to about 6 months, to match general release cycle for CHIP. Even if this changes at some point to anually, this still seems to be a more reasonable default if we actively triage and manage issues and PRs.
1 parent b90334a commit 1000d7e

File tree

1 file changed

+6
-16
lines changed

1 file changed

+6
-16
lines changed

.github/workflows/stale.yaml

+6-16
Original file line numberDiff line numberDiff line change
@@ -16,27 +16,17 @@ jobs:
1616
with:
1717
stale-issue-message:
1818
"This issue has been automatically marked as stale because
19-
it has not had recent activity. It will be closed if no
20-
further activity occurs. Remove stale label or comment or
21-
this will be closed in 30 days."
19+
it has not had recent activity."
2220
stale-pr-message:
2321
"This pull request has been automatically marked as stale
24-
because it has not had recent activity. It will be closed
25-
if no further activity occurs. Remove stale label or
26-
comment or this will be closed in 10 days."
22+
because it has not had recent activity."
2723
close-issue-message:
2824
"This stale issue has been automatically closed. Thank you
2925
for your contributions."
3026
close-pr-message:
3127
"This stale pull request has been automatically closed.
3228
Thank you for your contributions."
33-
days-before-issue-stale: 30
34-
days-before-issue-close: -1 # Don't close them for now
35-
days-before-pr-stale: 90
36-
days-before-pr-close: 10
37-
exempt-issue-labels:
38-
"security,blocked,cert blocker,build issue,Spec XML
39-
align,CI/CD improvements,memory"
40-
exempt-pr-labels:
41-
"security,blocked,cert blocker,build issue,Spec XML
42-
align,CI/CD improvements,memory"
29+
days-before-issue-stale: 180
30+
days-before-issue-close: -1 # Don't close stale issues
31+
days-before-pr-stale: 180
32+
days-before-pr-close: -1 # Don't close stale PRs

0 commit comments

Comments
 (0)