When other issues refer to a stale issue, don't mark it as stale, especially if closed as a duplicate of to-be-stale issue

Open
#1,324 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, typescript
Domain
ci-cd, devtools

Research direction

Start by examining how the action determines whether an issue is stale and how GitHub duplicate relationships or references could be detected. Done means canonical issues referenced by duplicate issues are not marked stale, with regression coverage for the reported cases.

Written by the indexing model from the issue text.

Description

feature request

Description:

When I close an issue as a duplicate of another issue, the bot shouldn't mark the another issue as a stale.

Justification:

For example I recently closed https://github.com/krille-chan/fluffychat/issues/2602 and https://github.com/krille-chan/fluffychat/issues/2147 as duplicates of https://github.com/krille-chan/fluffychat/issues/89 and https://github.com/krille-chan/fluffychat/issues/334 and today the bot decided to start commenting that the canonical issues have had no activity and will be closed.

GitHub issues natively support marking issues as duplicates of other issues and I would hope that information is accessible to the bot and thus it could take that and when that happened into consideration before marking issues as stale, if not even the fact that canonical issues have been referred to from other issues.

Are you willing to submit a PR?

I fear I don't have the skills required for that.

Dominant language
TypeScript
Stars
1.7k
Forks
438
Avg merge
27d 8h
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from actions/stale

All issues in actions/stale

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.