ci: add actions/stale workflow for issues

cchanche · cchanche · commit 941dba43b441 · 2026-03-06T18:28:34.000+01:00
diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml
@@ -0,0 +1,35 @@
+name: Close Stale Issues
+
+on:
+  schedule:
+    # Run every day at 2:00 AM UTC
+    - cron: '0 2 * * *'
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@v9
+        with:
+          repo-token: ${{ secrets.GITHUB_TOKEN }}
+          # Only process issues with the info-needed label (can have other labels too)
+          any-of-issue-labels: 'info-needed'
+          # Days before an issue with the info-needed label is considered stale
+          days-before-issue-stale: 30
+          # Days before closing a stale issue (7 day delay after marking as stale)
+          days-before-issue-close: 7
+          # Don't process pull requests
+          days-before-pr-stale: -1
+          days-before-pr-close: -1
+          stale-issue-label: 'stale'
+          close-issue-label: 'closed-by-stale'
+          # Remove stale label when issue receives comments/updates
+          remove-issue-stale-when-updated: true
+          # Customized messages
+          stale-issue-message: |
+            This issue has been inactive for 30 days with the `info-needed` label.
+            Please provide the requested information to keep this issue open.
+            This issue will be closed in 7 days if no response is provided.
+          close-issue-message: |
+            This issue has been closed because it has been inactive for 30 days with the `info-needed` label and no information was provided.
+            If you have additional context or want to reopen this issue, please comment and we'll be happy to help!
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -28,6 +28,22 @@ Here are a few things you can do that will increase the likelihood of your pull
 
 Work in Progress pull requests are also welcome to get feedback early on, or if there is something blocked you.
 
+## Issue Management Policy
+
+To maintain project health and keep issues actionable, we automatically manage stale issues using the following policy:
+
+**Stale Issue Closure**: Issues labeled with `info-needed` that remain inactive for 30 days will be automatically marked as stale. After an additional 7-day grace period, the issue will be closed if no response is provided.
+
+When an issue is marked as stale, we'll post a comment asking you to provide the requested information. If you respond with the information or show continued interest, the stale label will be removed and the issue will remain open.
+
+This policy helps us:
+
+- Keep the issue tracker focused on active issues
+- Encourage timely responses to information requests
+- Ensure discussions don't get lost in an ever-growing issue backlog
+
+If your issue was closed due to inactivity but you still have relevant information or context, please feel free to reopen it by commenting on the issue or opening a new one.
+
 ## Resources
 
 - [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
