Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine
Slack Integration - Find a way to consolidate change request & reimbursement notifications
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36
- Forks
- 9
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 11
Description
Spike Type
No response
Goal
Right now, if someone makes several change requests after each other relating to similar things, the related slack channel is spammed with messages from the finishline slackbot. Find a way to consolodate this messages - this could be within a thread, but this would involve reworking how we do update notifications.
Same goes for reimbursement requests.
Reason for Spike
We don't want slackbot notifications to take over our slack channels
Additional notes
No response
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
The issue does not name any files, tests, or entry points. Begin by locating the FinishLine Slackbot notification paths for change requests and reimbursement requests, then determine how related notifications are currently emitted. Done should mean a decided and implemented consolidation approach that reduces channel spam for both notification types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100