···11-name: "Close stale issues"
22-on:
33- schedule:
44- - cron: "0 0 * * *"
55- push:
66- paths:
77- - .github/workflows/stale.yml
88-99-jobs:
1010- stale:
1111- runs-on: ubuntu-latest
1212- steps:
1313- - uses: actions/stale@v2
1414- with:
1515- repo-token: ${{ secrets.GITHUB_TOKEN }}
1616- stale-issue-message: >-
1717- This issue has been automatically marked as stale because it has not
1818- had recent activity. It will be closed if no further activity
1919- occurs. The main purpose of this is to keep the issue tracker
2020- focused to what is actively being worked on, so that the amount and
2121- variety of open yet inactive issues does not overwhelm contributors.
2222-2323-2424-2525- An issue closed as stale is not rejected — further discussion is
2626- welcome in its closed state, and it can be resurrected at any time.
2727- odoc maintainers regularly check issues that were closed as stale in
2828- the past, to see if the time is right to reopen and work on them
2929- again. PRs addressing issues closed as stale are as welcome as PRs
3030- for open issues. They will be given the same review attention, and
3131- any other help.
3232- days-before-stale: 365
3333- days-before-close: -1
3434- exempt-issue-labels: "bug,not stale"
3535- stale-issue-label: "stale"