community_close_stale_issues.yml

name: "Close Stale Issues"
on:
  schedule:
    - cron: "0 2 * * 5"
  workflow_dispatch:
    inputs:
      debug-only:
        description: "Run in dry-run mode (no changes made)"
        type: boolean
        default: false
      operations-per-run:
        description: "Max number of issues to process (default: 1000)"
        type: number
        default: 1000

jobs:
  stale:
    if: github.repository_owner == 'zed-industries'
    runs-on: namespace-profile-2x4-ubuntu-2404
    steps:
      - uses: actions/stale@997185467fa4f803885201cee163a9f38240193d # v10
        with:
          repo-token: ${{ secrets.GITHUB_TOKEN }}
          stale-issue-message: >
            Zed development moves fast and a significant number of bugs become outdated.
            If you can reproduce this bug on the latest stable Zed, please let us know by leaving a comment with the Zed version,
            it helps us focus on the right issues.
            If the bug doesn't appear for you anymore, feel free to close the issue yourself; otherwise, the bot will close it in a couple of weeks.
            But even after it's closed by the bot, you can leave a comment with the version where the bug is reproducible and we'll reopen the issue.
            Thanks!
          close-issue-message: "This issue was closed due to inactivity. If you're still experiencing this problem, please leave a comment with your Zed version so that we can reopen the issue."
          days-before-stale: 90
          days-before-close: 21
          only-issue-types: "Bug,Crash"
          operations-per-run: ${{ inputs.operations-per-run || 2000 }}
          ascending: true
          enable-statistics: true
          debug-only: ${{ inputs.debug-only }}
          stale-issue-label: "stale"
          exempt-issue-labels: "never stale"