Don't react with :potato: on messages that mention Junior
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- backend
Research direction
No file or test is named in the issue. Start by locating the TypeScript entry point that handles Junior's Slack reactions and checking how mentions are detected. Done means messages mentioning Junior's own user ID receive text gratitude instead of a 🥔 reaction, while other users' messages retain the reaction.
Written by the indexing model from the issue text.
Description
Problem
When Junior reacts with 🥔 on a Slack message where it is mentioned, the gib-potato bot interprets it as Junior trying to send a potato to itself. This doesn't work and wastes the reaction.
Expected behavior
Junior should only use 🥔 reactions on messages from other users where Junior is not mentioned. When Junior is mentioned in the message, it should express gratitude in text instead of reacting.
Context
This is a persona/behavior rule: the 🥔 emoji is Junior's signature gratitude reaction, but it needs to skip reacting when the message contains a mention of Junior's own user ID.
Action taken on behalf of Michi Hoffmann.
- Dominant language
- TypeScript
- Stars
- 362
- Forks
- 38
- Avg merge
- 5h 9m
- Merged PRs (30d)
- 166
Getting set up
- Ships a Dockerfile or Docker Compose file
- No 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 getsentry/junior
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
All issues in getsentry/junior
Similar issues
-
area:docs bug triage:confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Cotal-AI/Cotal#2875 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
anomalyco/models.dev#8862 · 1 comment ·
Maintainers usually reply within 1 day
-
fix(data-lake): wizard source step still previews the local slug, not the server-disambiguated onePossibly taken A pull request linked to this issue is open or already merged. Opendata-lake
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
ready-for-triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
konflux-ci/konflux-ui#1596 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day