[Bug] Processing of issues via bot: stale label is set but not removed
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### Version
all
### Minimal reproduce step
look at issues with stale labels e.g. https://github.com/apache/pulsar/issues/18348
### What did you expect to see?
when stale label is added automatically,
it should also be removed automatically if
- an issue is newly commented or
- maybe even if it's mentioned some else.
### What did you see instead?
stale label stays forever
Example:
https://github.com/apache/pulsar/issues/18348
Automatically set to stale via bot on December 19, 2022
commented on September 28, 2023
mentioned on October 27, 2023
still stale on October 28, 2023
otherwise if fixed or could not be reproduced it should be closed
### Anything else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Contributor guide
Research direction
Start by tracing the automation responsible for stale labels and use issue 18348 as the reproduction case, comparing its stale-label and comment history. Confirm the intended behavior for new comments and mentions, then verify that the stale label is removed automatically and that the agreed behavior is covered by the available automation checks.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100