When your subscription expires, we tell you about it a few too many times
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Ruby
- Stars
- 6
- Forks
- 1
- Avg merge
- 9m
- Merged PRs (30d)
- 4
Description
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
Start by reproducing the subscription-expiration scenario shown in the screenshot and trace where the expiration notification is generated. Done means the user receives the expiration notice only once rather than several times.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100