Skip to content

doc: add section stating that very stale PRs should be closed #57541

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

Merged
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions doc/contributing/pull-requests.md
Original file line number Diff line number Diff line change
Expand Up @@ -446,6 +446,17 @@ credit for the work they started (either by preserving their name and email
address) in the commit log, or by using an `Author:` meta-data tag in the
commit.

If a pull request has been inactive for more than six months, it is unlikely
to be merged. The contributor may no longer be engaged, may have lost context
on their changes, the Node.js codebase may have evolved to the point where
resuming the effort is impractical, or all of the above.
To keep the project well organized and more maintainable, such stale pull
requests should generally be closed unless they provide clear ongoing value
or have a well defined path forward. When closing a pull request, always
leave a polite comment explaining the reason and encouraging the contributor
to restart the effort and submit a new pull request if the changes are still
relevant and applicable.

### Approving a change

Any Node.js core collaborator (any GitHub user with commit rights in the
Expand Down
Loading