|
| 1 | +# SPDX-FileCopyrightText: 2025 Free Software Foundation Europe e.V. <https://fsfe.org> |
| 2 | +# |
| 3 | +# SPDX-License-Identifier: GPL-3.0-or-later |
| 4 | + |
| 5 | +name: Close inactive issues |
| 6 | +on: |
| 7 | + schedule: |
| 8 | + - cron: "22 2 * * *" |
| 9 | + |
| 10 | +jobs: |
| 11 | + close-issues: |
| 12 | + runs-on: ubuntu-latest |
| 13 | + permissions: |
| 14 | + issues: write |
| 15 | + pull-requests: write |
| 16 | + steps: |
| 17 | + - uses: actions/stale@v9 |
| 18 | + with: |
| 19 | + days-before-issue-stale: 360 |
| 20 | + days-before-issue-close: 30 |
| 21 | + operations-per-run: 5 |
| 22 | + remove-stale-when-updated: false |
| 23 | + exempt-all-issue-assignees: true |
| 24 | + stale-issue-label: "stale" |
| 25 | + close-issue-label: "unresolved" |
| 26 | + stale-issue-message: |
| 27 | + "Thank you for your time and contributions! Unfortunately, this |
| 28 | + issue has been inactive for quite a while which means we probably |
| 29 | + can't manage the time to deal with it. That's why we're marking it |
| 30 | + as stale. We want to keep things tidy and focus on active |
| 31 | + discussions, but we’re always happy to revisit if this is still |
| 32 | + relevant!\n\nIf you’d like to keep this open, please add a comment |
| 33 | + to let us know and remove the label stale. Otherwise, this issue |
| 34 | + will most likely be automatically closed soon." |
| 35 | + close-issue-message: |
| 36 | + "Since there hasn't been any recent activity after the last message, |
| 37 | + we're going to go ahead and close this issue. Feel free to reopen |
| 38 | + this and remove the labels stale and unresolved if it's |
| 39 | + urgent.\n\nWe truly appreciate your contributions and |
| 40 | + engagement!\n\nThank you and happy hacking!" |
| 41 | + days-before-pr-stale: -1 |
| 42 | + days-before-pr-close: -1 |
| 43 | + stale-pr-label: "stale" |
| 44 | + close-pr-label: "unresolved" |
| 45 | + stale-pr-message: |
| 46 | + "Thank you so much for your contribution! We really appreciate your |
| 47 | + time and effort on this! However, this pull request has been |
| 48 | + inactive for a while, which means we have not been able to |
| 49 | + prioritize it. It also means there are most likely merge conflicts |
| 50 | + or required updates to bring it in line with the latest changes. To |
| 51 | + keep things organized and focus on active contributions, we're |
| 52 | + marking this as stale.\n\nIf this is still relevant and you'd like |
| 53 | + to keep it open, please update the branch and remove the label |
| 54 | + stale. Otherwise, this PR may be automatically closed soon. We're |
| 55 | + always happy to revisit if needed!" |
| 56 | + close-pr-message: |
| 57 | + "Since there hasn't been any recent activity after the last message, |
| 58 | + we're going to go ahead and close this pull request. If this is |
| 59 | + still relevant to you, feel free to reopen it and update the branch |
| 60 | + to resolve any conflicts. In that case, please also remove the |
| 61 | + labels stale and unresolved.\n\nWe truly appreciate your |
| 62 | + contributions and engagement!\n\nThank you and happy hacking!" |
| 63 | + repo-token: ${{ secrets.GITHUB_TOKEN }} |
0 commit comments