Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

meta: merge stalebot and update timings/messages #52712

Closed
wants to merge 11 commits into from
56 changes: 0 additions & 56 deletions .github/workflows/close-stale-feature-requests.yml

This file was deleted.

59 changes: 0 additions & 59 deletions .github/workflows/close-stale-pull-requests.yml

This file was deleted.

46 changes: 46 additions & 0 deletions .github/workflows/close-stale.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
name: Close stale issues and PRs
on:
workflow_dispatch:
schedule:
# Run every day at 1:00 AM UTC.
- cron: 0 1 * * *
# yamllint disable rule:empty-lines
env:
CLOSE_MESSAGE: >
There hasn't been any activity on this issue/PR for over 8 months.
We appreciate your contribution, but since there hasn't been any
progress recently, we're closing it. If you disagree with this
decision, please leave a comment.

WARN_MESSAGE: >
There hasn't been any activity on this issue/PR for over 7 months.
We appreciate your contribution, but since there hasn't been any
progress recently, we're closing it in **30 days**. If you
disagree with this decision, please leave a comment.
# yamllint enable

permissions:
actions: write
issues: write
pull-requests: write

jobs:
stale:
if: github.repository == 'nodejs/node'
runs-on: ubuntu-latest
steps:
- uses: actions/stale@28ca1036281a5e5922ead5184a1bbf96e5fc984e # v9.0.0
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
days-before-stale: 240
days-before-close: 30
close-issue-message: ${{ env.CLOSE_MESSAGE }}
stale-issue-message: ${{ env.WARN_MESSAGE }}
close-pr-message: ${{ env.CLOSE_MESSAGE }}
stale-pr-message: ${{ env.WARN_MESSAGE }}
exempt-issue-labels: never-stale
exempt-pr-labels: never-stale
stale-issue-label: stale
stale-pr-label: stale
operations-per-run: 50
remove-stale-when-updated: true
35 changes: 0 additions & 35 deletions doc/contributing/feature-request-management.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,38 +52,3 @@ 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).
```
23 changes: 23 additions & 0 deletions doc/contributing/issues.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,5 +60,28 @@ activities, such as applying labels and closing/reopening/assigning issues.
For more information on the roles and permissions, see ["Permission levels for
repositories owned by an organization"](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization).

## Handling stale issues

Once there has been no activity on a issue for
7 months, the following comment will be added:

```markdown
There hasn't been any activity on this issue/PR for over 7 months.
We appreciate your contribution, but since there hasn't been any
progress recently, we're closing it in **30 days**. If you
disagree with this decision, please leave a comment.
```

If there is no additional activity/discussion on the
issue in the next month (totalling to 8 months), it is
closed, and the following comment is added:

```markdown
There hasn't been any activity on this issue/PR for over 8 months.
We appreciate your contribution, but since there hasn't been any
progress recently, we're closing it. If you disagree with this
decision, please leave a comment.
```

[Node.js help repository]: https://github.com/nodejs/help/issues
[Technical Steering Committee (TSC) repository]: https://github.com/nodejs/TSC/issues
Loading