bytecodealliance / bytecodealliance/subscribe-to-label-action
Avoid spurious mentions
Open
enhancement
- Dominant language
- JavaScript
- Stars
- 12
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
There are two cases where we could avoid mentioning the user:
- the user authored the issue/PR we're considering
- the user has been already manually mentioned (in the first message, or before the bot saw all the issues, e.g. when it got throttled by Github API rate limits)
Contributor guide
Research direction
Start by tracing the JavaScript GitHub Action's label-application and mention logic. Check how issue or pull-request authors and existing manual mentions are represented, then verify that those users are not mentioned again while other subscribers still are.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100