Skip to content

meta: broaden stale bot - #62658

Merged
nodejs-github-bot merged 2 commits into
nodejs:mainfrom
avivkeller:broaden-stale-bot
Apr 18, 2026
Merged

nodejs-github-bot merged 2 commits into
nodejs:mainfrom
avivkeller:broaden-stale-bot

Conversation

@avivkeller

@avivkeller avivkeller commented Apr 9, 2026 •

Copy link
Copy Markdown
Member

As it currently stands, in order for an issue or PR to be marked as stale, the following conditions must be true:


(For issues)

  1. The issue must be labeled feature request
  2. The issue must not be labeled never-stale
  3. The issue must have had no activity for 210 days, with a warning posted at day 180.

(For PRs)

  1. The PR must not be labeled never-stale
  2. The PR must be older than 525600 minutes (1 year)
  3. The issue must have had no activity for 180 days, with a warning posted at day 150.

I propose we change this to cover more issues and pull requests, following this new configuration:

  1. The issue or PR must not be labeled never-stale. If an issue, this also includes confirmed-bug.
  2. The issue or PR must have no activity for 240 days, with a warning posted at day 210.

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.

Copilot AI review requested due to automatic review settings April 9, 2026 19:18
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/actions
  • @nodejs/tsc