aboutsummaryrefslogtreecommitdiff
path: root/.github/workflows
diff options
context:
space:
mode:
authorh1dden-da3m0n <33120068+h1dden-da3m0n@users.noreply.github.com>2022-01-23 17:02:41 +0100
committerh1dden-da3m0n <33120068+h1dden-da3m0n@users.noreply.github.com>2022-01-23 17:02:41 +0100
commit28f4d574f7af415839bdeb5ba43dbed595553f4b (patch)
tree1189fbca73a05af9a81084eac5df6d2c6b4cb319 /.github/workflows
parentea3d79c0eb10d07f1bb6e653ee0496a7c2ded720 (diff)
add stale issue check workflow
this should replace the functionality of the discontinued stale-bot
Diffstat (limited to '.github/workflows')
-rw-r--r--.github/workflows/repo-stale.yaml30
1 files changed, 30 insertions, 0 deletions
diff --git a/.github/workflows/repo-stale.yaml b/.github/workflows/repo-stale.yaml
new file mode 100644
index 000000000..3dca44122
--- /dev/null
+++ b/.github/workflows/repo-stale.yaml
@@ -0,0 +1,30 @@
+name: Issue Stale Check
+
+on:
+ schedule:
+ - cron: '30 1 * * *'
+ workflow_dispatch:
+
+permissions:
+ issues: write
+ pull-requests: write
+
+jobs:
+ stale:
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/stale@v4.1.0
+ with:
+ repo-token: ${{ github.token }}
+ days-before-stale: 120
+ days-before-pr-stale: -1
+ days-before-close: 21
+ days-before-pr-close: -1
+ exempt-issue-labels: regression,security,roadmap,future,feature,enhancement,confirmed
+ stale-issue-label: stale
+ stale-issue-message: |-
+ This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
+
+ If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
+
+ This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on [Matrix or Social Media](https://docs.jellyfin.org/general/getting-help.html).