This action closes issues where a maintainer or contributor has not responded or otherwise acted upon the issue.

Open
#1,122 20 comments 3 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
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
devops, tooling

Research direction

Start by reproducing the default action behavior described in the issue, focusing on issues where only the reporter has interacted for 60 days. Review how maintainer or contributor responses are distinguished from reporter activity. Done means unanswered reporter issues remain open, while reporter abandonment can still be detected after someone else responds.

Written by the indexing model from the issue text.

Description

feature request

Repro steps:
I open an issue in a repo where I am not a contributor or maintainer, because I need help or have a question about something. This action is enabled in the repo using the defaults. None of the listed maintainers or contributors comments on the issue for 60 days.

Expected behavior:
If it was answered in the meantime I would update and close the issue but that has not happened in this case. I still need help or have a question, its not likely a great priority or emergency for me after this much time, but still I expect nothing to happen to the issue and for it to remain open until someone from the repo can respond.

Actual behavior:
This action rather rudely informs me the issue will be closed in 7 days.

I get that there are cases where reporters abandon issues, and am totally OK with that - I think 2 weeks is a generous amount of time before declaring reporter abandonment. But it only counts as reporter abandonment when someone other than the reporter has given some kind of response. That is not happening here, and it was the same thing with the stalebot,

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.