meta: broaden stale bot

Author: avivkeller

.github/workflows/close-stale-pull-requests.yml

@@ -1,4 +1,4 @@
-name: Close stale feature requests
+name: Close stale
 on:
   workflow_dispatch:
   schedule:
@@ -8,26 +8,17 @@ on:
 # yamllint disable rule:empty-lines
 env:
   CLOSE_MESSAGE: >
-    There has been no activity on this feature request
-    and it is being closed. If you feel closing this issue is not the
-    right thing to do, please leave a comment.
+    This issue has been automatically closed after 30 days of inactivity
+    following its stale status (no activity for a total of 210 days).
 
-
-    For more information on how the project manages
-    feature requests, please consult the
-    [feature request management document](https://github.com/nodejs/node/blob/HEAD/doc/contributing/feature-request-management.md).
+    If this is still relevant, feel free to reopen it or leave a comment
+    with additional details so we can continue the discussion.
 
   WARN_MESSAGE: >
-    There has been no activity on this feature request for
-    5 months. To help maintain relevant open issues, please
-    add the https://github.com/nodejs/node/labels/never-stale
-    label or close this issue if it should be closed. If not,
-    the issue will be automatically closed 6 months after the
-    last non-automated comment.
+    This issue has been marked as stale due to 180 days of inactivity.
 
-    For more information on how the project manages
-    feature requests, please consult the
-    [feature request management document](https://github.com/nodejs/node/blob/HEAD/doc/contributing/feature-request-management.md).
+    It will be automatically closed in 30 days if no further activity occurs.
+    If this is still relevant, please leave a comment or update it to keep it open.
 # yamllint enable
 
 permissions:
@@ -47,10 +38,13 @@ jobs:
           days-before-stale: 180
           days-before-close: 30
           stale-issue-label: stale
+          exempt-issue-labels: never-stale
           close-issue-message: ${{ env.CLOSE_MESSAGE }}
           stale-issue-message: ${{ env.WARN_MESSAGE }}
-          only-labels: feature request
-          exempt-issue-labels: never-stale
+          stale-pr-label: stale
+          exempt-pr-labels: never-stale
+          close-pr-message: ${{ env.CLOSE_MESSAGE }}
+          stale-pr-message: ${{ env.WARN_MESSAGE }}
           # max requests it will send per run to the GitHub API before it deliberately exits to avoid hitting API rate limits
           operations-per-run: 500
           remove-stale-when-updated: true

…rkflows/close-stale-feature-requests.yml .github/workflows/stale.yml.github/workflows/close-stale-feature-requests.yml renamed to .github/workflows/stale.yml .github/workflows/close-stale-feature-requests.yml renamed to .github/workflows/stale.yml

@@ -42,50 +42,10 @@ Individual collaborators review issues marked as `feature request`
 along with other issues and may or may not decide to
 work on an implementation or advocate on their behalf.
 
-If a collaborator believes a feature request must be implemented
-they can add the `never-stale` label to the issue and it will
-be excluded from the automated feature request handling
-as outlined below.
-
 ## Expressing support for a feature request
 
 If you come across a feature request and want to add your
 support for that feature please express your support
 with the thumbs up emoji as a reaction. At some point in the
 future we may use this as additional input in the automated
 handling of feature requests.
-
-## Automated feature request handling
-
-Our experience is that most feature requests that are
-likely to be addressed, will be addressed within the first
-6 months after they are submitted.
-
-Once there has been no activity on a feature request for
-5 months, the following comment will be added
-to the issue:
-
-```markdown
-There has been no activity on this feature request for
-5 months and it is unlikely to be implemented.
-It will be closed 6 months after the last non-automated comment.
-
-For more information on how the project manages
-feature requests, please consult the
-[feature request management document](https://github.com/nodejs/node/blob/HEAD/doc/contributing/feature-request-management.md).
-```
-
-If there is no additional activity/discussion on the
-feature request in the next month, the following
-comment is added to the issue and the issue will be
-closed:
-
-```markdown
-There has been no activity on this feature request
-and it is being closed. If you feel closing this issue is not the
-right thing to do, please leave a comment.
-
-For more information on how the project manages
-feature requests, please consult the
-[feature request management document](https://github.com/nodejs/node/blob/HEAD/doc/contributing/feature-request-management.md).
-```