Add option to keep posting comment on 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
- typescript
Research direction
The issue names the actions/stale@v9 configuration and the proposed comment-stale-issue option, but no source files or tests. Start by locating the stale issue processing and configuration entry points, then trace how stale comments and repeat runs are handled. Done means the option is documented and enabled runs post the configured message while the issue remains stale, stopping when it is updated or closed.
Written by the indexing model from the issue text.
Description
Description:
Currently the stale bot
- Add a label "stale"
- Poste a message "This is stale"
And then, if the user is doing nothing, finally close the issue.
But I'd like the bot to keep posting "This is stale" on the issue every day to ping the user until
- The issue is not stale
- Or the issue is closed
So I would like an option in order to force the actions to keep running on stale issue and re-post a comment.
Like a comment-stale-issue: true (false by default)
Justification:
I'm using the stale bot to post a message on issue under some conditions, like a missing label.
For instance
- name: Check for issues without priority
uses: actions/stale@v9
with:
ascending: false
days-before-stale: 7
days-before-pr-stale: -1
days-before-close: -1
ignore-updates: true
exempt-issue-labels: priority:low,priority:medium,priority:high,priority:critical
stale-issue-label: need:priority
stale-issue-message: >
This issue is missing a priority.
And I'd like that until the condition is met, the stale bot is still posting a new remember every day (when the github action is running), in order to ping the author which might have forgotten.
Are you willing to submit a PR?
- Sure, but I don't know how this work ; I assume the dev is not that hard, but I would help some explanations about the needed change and where is the core logic.
- 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
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
db-ux-design-system/core-web#8856 ·
Maintainers usually reply within 1 day
-
'!' breaking change is lost when the commit also has an empty BREAKING CHANGE footerPossibly taken @wittdennis claimed this today. Openpriority: p3 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
googleapis/release-please#2971 ·
Maintainers usually reply within 1 day
-
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