Commit 5e14e4d
File tree
- .github/workflows
- doc/contributing
This file was deleted.
This file was deleted.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -0,0 +1,50 @@ | |||
| 1 | + name: Close stale | ||
| 2 | + on: | ||
| 3 | + workflow_dispatch: | ||
| 4 | + schedule: | ||
| 5 | + # Run every day at 1:00 AM UTC. | ||
| 6 | + - cron: 0 1 * * * | ||
| 7 | + | ||
| 8 | + # yamllint disable rule:empty-lines | ||
| 9 | + env: | ||
| 10 | + CLOSE_MESSAGE: > | ||
| 11 | + This {0} has been automatically closed after 30 days of inactivity | ||
| 12 | + following its stale status (no activity for a total of 240 days). | ||
| 13 | + | ||
| 14 | + If this is still relevant, feel free to reopen it or leave a comment | ||
| 15 | + with additional details so we can continue the discussion. | ||
| 16 | + | ||
| 17 | + WARN_MESSAGE: > | ||
| 18 | + This {0} has been marked as stale due to 210 days of inactivity. | ||
| 19 | + | ||
| 20 | + It will be automatically closed in 30 days if no further activity occurs. | ||
| 21 | + If this is still relevant, please leave a comment or update it to keep it open. | ||
| 22 | + # yamllint enable | ||
| 23 | + | ||
| 24 | + permissions: | ||
| 25 | + contents: read | ||
| 26 | + | ||
| 27 | + jobs: | ||
| 28 | + stale: | ||
| 29 | + permissions: | ||
| 30 | + issues: write # for actions/stale to close stale issues | ||
| 31 | + pull-requests: write # for actions/stale to close stale PRs | ||
| 32 | + if: github.repository == 'nodejs/node' | ||
| 33 | + runs-on: ubuntu-slim | ||
| 34 | + steps: | ||
| 35 | + - uses: actions/stale@b5d41d4e1d5dceea10e7104786b73624c18a190f # v10.2.0 | ||
| 36 | + with: | ||
| 37 | + repo-token: ${{ secrets.GITHUB_TOKEN }} | ||
| 38 | + days-before-stale: 210 | ||
| 39 | + days-before-close: 30 | ||
| 40 | + stale-issue-label: stale | ||
| 41 | + exempt-issue-labels: never-stale, confirmed-bug | ||
| 42 | + close-issue-message: ${{ format(env.CLOSE_MESSAGE, 'issue') }} | ||
| 43 | + stale-issue-message: ${{ format(env.WARN_MESSAGE, 'issue') }} | ||
| 44 | + stale-pr-label: stale | ||
| 45 | + exempt-pr-labels: never-stale | ||
| 46 | + close-pr-message: ${{ format(env.CLOSE_MESSAGE, 'pull request') }} | ||
| 47 | + stale-pr-message: ${{ format(env.WARN_MESSAGE, 'pull request') }} | ||
| 48 | + # max requests it will send per run to the GitHub API before it deliberately exits to avoid hitting API rate limits | ||
| 49 | + operations-per-run: 500 | ||
| 50 | + remove-stale-when-updated: true | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -42,50 +42,10 @@ Individual collaborators review issues marked as `feature request` | |||
| 42 | 42 | along with other issues and may or may not decide to | |
| 43 | 43 | work on an implementation or advocate on their behalf. | |
| 44 | 44 | ||
| 45 | - If a collaborator believes a feature request must be implemented | ||
| 46 | - they can add the `never-stale` label to the issue and it will | ||
| 47 | - be excluded from the automated feature request handling | ||
| 48 | - as outlined below. | ||
| 49 | - | ||
| 50 | 45 | ## Expressing support for a feature request | |
| 51 | 46 | ||
| 52 | 47 | If you come across a feature request and want to add your | |
| 53 | 48 | support for that feature please express your support | |
| 54 | 49 | with the thumbs up emoji as a reaction. At some point in the | |
| 55 | 50 | future we may use this as additional input in the automated | |
| 56 | 51 | handling of feature requests. | |
| 57 | - | ||
| 58 | - ## Automated feature request handling | ||
| 59 | - | ||
| 60 | - Our experience is that most feature requests that are | ||
| 61 | - likely to be addressed, will be addressed within the first | ||
| 62 | - 6 months after they are submitted. | ||
| 63 | - | ||
| 64 | - Once there has been no activity on a feature request for | ||
| 65 | - 5 months, the following comment will be added | ||
| 66 | - to the issue: | ||
| 67 | - | ||
| 68 | - ```markdown | ||
| 69 | - There has been no activity on this feature request for | ||
| 70 | - 5 months and it is unlikely to be implemented. | ||
| 71 | - It will be closed 6 months after the last non-automated comment. | ||
| 72 | - | ||
| 73 | - For more information on how the project manages | ||
| 74 | - feature requests, please consult the | ||
| 75 | - [feature request management document](https://github.com/nodejs/node/blob/HEAD/doc/contributing/feature-request-management.md). | ||
| 76 | - ``` | ||
| 77 | - | ||
| 78 | - If there is no additional activity/discussion on the | ||
| 79 | - feature request in the next month, the following | ||
| 80 | - comment is added to the issue and the issue will be | ||
| 81 | - closed: | ||
| 82 | - | ||
| 83 | - ```markdown | ||
| 84 | - There has been no activity on this feature request | ||
| 85 | - and it is being closed. If you feel closing this issue is not the | ||
| 86 | - right thing to do, please leave a comment. | ||
| 87 | - | ||
| 88 | - For more information on how the project manages | ||
| 89 | - feature requests, please consult the | ||
| 90 | - [feature request management document](https://github.com/nodejs/node/blob/HEAD/doc/contributing/feature-request-management.md). | ||
| 91 | - ``` | ||
0 commit comments