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
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
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
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
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from actions/stale
-
Stale label remains after pushing a new commitPossibly taken @v-chiranjib-swain claimed this 21 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Closing items while paginating can skip open pull requestsPossibly taken @v-chiranjib-swain claimed this 93 days ago. Openbug
-
Ignore issues which has linked open PRsPossibly taken A pull request linked to this issue is open or already merged. Openfeature request
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
feature request
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 1/5 1-3 hours Newbie friendliness 69/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/symphony#91 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
solidjs/solid-docs#1716 ·
Maintainers usually reply within 1 day