Skip to content

Commit 7f05db5

Browse files
authored
Add configuration for stale bot (#1460)
1 parent a085b6b commit 7f05db5

File tree

1 file changed

+54
-0
lines changed

1 file changed

+54
-0
lines changed

.github/workflows/stale.yml

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
# See https://github.com/marketplace/actions/close-stale-issues
2+
3+
name: Mark stale issues and pull requests
4+
5+
on:
6+
schedule:
7+
# run at 21:30 UTC daily
8+
- cron: "30 21 * * *"
9+
10+
jobs:
11+
stale:
12+
runs-on: ubuntu-latest
13+
14+
steps:
15+
- uses: actions/stale@v10
16+
with:
17+
repo-token: ${{ secrets.GITHUB_TOKEN }}
18+
19+
permissions:
20+
actions: write
21+
issues: write
22+
pull-requests: write
23+
24+
# The number of days old an issue can be before marking it stale.
25+
days-before-stale: 180
26+
# Number of days of inactivity before a stale issue is closed
27+
days-before-close: 30
28+
29+
# Label to use when marking an issue as stale
30+
stale-issue-label: 'Can Close?'
31+
stale-pr-label: 'Can Close?'
32+
33+
stale-issue-message: >
34+
Thanks for your contributions to rules_kotlin!
35+
36+
This issue has been automatically marked as stale because it has not had
37+
any activity for 180 days.
38+
It will be closed if no further activity occurs in 30 days.
39+
40+
41+
stale-pr-message: >
42+
Thanks for your contributions to rules_kotlin!
43+
44+
This Pull Request has been automatically marked as stale because it has not had
45+
any activity for 180 days.
46+
It will be closed if no further activity occurs in 30 days.
47+
48+
close-issue-message: >
49+
This issue was automatically closed because it went 30 days without a reply
50+
since it was labeled "Can Close?"
51+
52+
close-pr-message: >
53+
This PR was automatically closed because it went 30 days without a reply
54+
since it was labeled "Can Close?"

0 commit comments

Comments
 (0)