Open
Conversation
Collaborator
|
Review requested:
|
nodejs-github-bot
added
the
meta
avivkeller
force-pushed
the
broaden-stale-bot
branch
from
3184085 to
d79d8b4
Compare
There was a problem hiding this comment.
Pull request overview
Broadens and unifies the repository’s stale-item automation by expanding the stale workflow beyond feature-request-only issues and folding PR staleness handling into the same workflow, while removing now-obsolete feature-request automation documentation and a dedicated PR-stale workflow.
Changes:
- Updates
.github/workflows/stale.ymlto runactions/stalefor both issues and pull requests (and removes the “feature request only” targeting). - Removes the standalone PR stale workflow (
close-stale-pull-requests.yml) in favor of the unified stale workflow. - Simplifies
feature-request-management.mdby removing the automated feature request handling section.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
doc/contributing/feature-request-management.md |
Removes documented automated feature-request stale/close process and related never-stale guidance. |
.github/workflows/stale.yml |
Broadens stale bot to apply to both issues and PRs, updates messages, and adds PR configuration. |
.github/workflows/close-stale-pull-requests.yml |
Deletes the older, separate PR stale-closure workflow. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
aduh95
reviewed
Apr 10, 2026
aduh95
approved these changes
Apr 10, 2026
aduh95
added
author ready
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As it currently stands, in order for an issue or PR to be marked as stale, the following conditions must be true:
(For issues)
feature requestnever-stale(For PRs)
never-staleI propose we change this to cover more issues and pull requests, following this new configuration:
never-stale. If an issue, this also includesconfirmed-bug.I understand this will likely incur a little bit of noise for the next run, but in the end, I think it'll help not just clean up the issue tracker, but draw attention to PRs that may have fallen through the cracks.