If a user wasn't paired, let them know
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Ruby
- Stars
- 6
- Forks
- 1
- Avg merge
- 9m
- Merged PRs (30d)
- 4
Description
That way, there is a consistent interaction with S'Up every week. Subset of dblock/slack-sup#27.
Contributor 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.
Research direction
No file, test, or entry point is named. Start by locating the weekly pairing flow and its user notifications, then determine how an unpaired user should be identified and notified. Done means users who receive no pairing get a consistent S'Up message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100