mirror of
https://github.com/zed-industries/zed.git
synced 2024-12-28 11:29:25 +00:00
87ac4cff60
@notpeter and I decided on these things: - Give users 10 days to respond - Only run once a week: Tuesday @7AM ET Release Notes: - N/A
31 lines
1.4 KiB
YAML
31 lines
1.4 KiB
YAML
name: "Close Stale Issues"
|
|
on:
|
|
schedule:
|
|
- cron: "0 11 * * 2"
|
|
workflow_dispatch:
|
|
|
|
jobs:
|
|
stale:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/stale@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. Are you able to reproduce this issue in the latest version of Zed? If so, please let us know by commenting on this issue and we will keep it open; otherwise, we'll close it in 10 days. Feel free to open a new issue if you're seeing this message after the issue has been closed.
|
|
|
|
Thanks for your help!
|
|
close-issue-message: "This issue was closed due to inactivity; feel free to open a new issue if you're still experiencing this problem!"
|
|
# 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: 10
|
|
any-of-issue-labels: "defect,panic / crash"
|
|
operations-per-run: 1000
|
|
ascending: true
|
|
enable-statistics: true
|
|
stale-issue-label: "stale"
|