mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-01-31 11:03:11 +08:00
46 lines
2.0 KiB
YAML
46 lines
2.0 KiB
YAML
name: "Automatically close stale issues"
|
|
on:
|
|
workflow_dispatch:
|
|
schedule:
|
|
- cron: "0 */6 * * *"
|
|
#Run every 6 hours
|
|
permissions: {}
|
|
|
|
jobs:
|
|
stale:
|
|
runs-on: ubuntu-latest
|
|
permissions:
|
|
actions: write
|
|
issues: write
|
|
steps:
|
|
- uses: actions/stale@997185467fa4f803885201cee163a9f38240193d # v10.1.1
|
|
with:
|
|
stale-issue-message: |-
|
|
We are clearing up our old `help`-issues and your issue has been open for 60 days with no activity.
|
|
If no comment is made and the stale label is not removed, this issue will be closed in 7 days.
|
|
days-before-stale: 60
|
|
days-before-close: 7
|
|
days-before-pr-stale: -1
|
|
days-before-pr-close: -1
|
|
exempt-issue-labels: "News,discussion,bug,doc,feature-request"
|
|
exempt-issue-assignees: "louislam"
|
|
operations-per-run: 200
|
|
- uses: actions/stale@997185467fa4f803885201cee163a9f38240193d # v10.1.1
|
|
with:
|
|
stale-issue-message: |-
|
|
This issue was marked as `cannot-reproduce` by a maintainer.
|
|
If an issue is non-reproducible, we cannot fix it, as we do not know what the underlying issue is.
|
|
If you have any ideas how we can reproduce this issue, we would love to hear them.
|
|
|
|
We don't have a good way to deal with truely unreproducible issues and are going to close this issue in a month.
|
|
If think there might be other differences in our environment or in how we tried to reproduce this, we would appreciate any ideas.
|
|
close-issue-message: |-
|
|
This issue will be closed as no way to reproduce it has been found.
|
|
If you/somebody finds a way how to (semi-reliably) reproduce this, we can reopen this issue. ^^
|
|
days-before-stale: 180
|
|
days-before-close: 30
|
|
days-before-pr-stale: -1
|
|
days-before-pr-close: -1
|
|
any-of-issue-labels: "cannot-reproduce"
|
|
operations-per-run: 200
|