Close Stale Issues #3
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
name: "Close Stale Issues" | |
on: | |
schedule: | |
- cron: "0 11 * * 2" | |
workflow_dispatch: | |
jobs: | |
stale: | |
runs-on: ubuntu-latest | |
steps: | |
- uses: actions/stale@28ca1036281a5e5922ead5184a1bbf96e5fc984e # v9 | |
with: | |
repo-token: ${{ secrets.GITHUB_TOKEN }} | |
stale-issue-message: > | |
Hi there! 👋 | |
We're working to clean up our issue tracker by closing older issues that might not be relevant anymore. If you are able to reproduce this issue in the latest version of Zed, please let us know by commenting on this issue, and we will keep it open. If you can't reproduce it, feel free to close the issue yourself. Otherwise, we'll close it in 7 days. | |
Thanks for your help! | |
close-issue-message: "This issue was closed due to inactivity. If you're still experiencing this problem, please open a new issue with a link to this issue." | |
# We will increase `days-before-stale` to 365 on or after Jan 24th, | |
# 2024. This date marks one year since migrating issues from | |
# 'community' to 'zed' repository. The migration added activity to all | |
# issues, preventing 365 days from working until then. | |
days-before-stale: 180 | |
days-before-close: 7 | |
any-of-issue-labels: "defect,panic / crash" | |
operations-per-run: 1000 | |
ascending: true | |
enable-statistics: true | |
stale-issue-label: "stale" |