This action closes issues where a maintainer or contributor has not responded or otherwise acted upon the issue.
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
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
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
- 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 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 1 day
-
🛠️ dette technique
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
betagouv/mon-entreprise#4752 · 1 comment ·
Maintainers usually reply within 5 days
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
franciscoBSalgueiro/en-croissant#1111 ·
Maintainers usually reply within 2 days
-
area/providers type/feature version/v2
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anomalyco/opencode#64845 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day