The act of closing an issue should be a thing: Achievements
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7
- Forks
- 3
- Avg merge
- 7m
- Merged PRs (30d)
- 3
Description
The act of closing an issue should be a thing which can be used to accumulate kudos and provide rewards.
What to call it?
An achievement. A Done That. A check mark. A crossing off the list.
We should design the system so that people get dopamine shots from these, both from getting them, and from sharing them, and possibly from others applauding them.
You should be able to look back on the week and see all the issues you -- or your team --- have closed.
Make them big/medium/small? Yes I think we have icons elephants mice etc.
You should be able to drop an achievement into a chat for example to get encouragement.
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
No files, tests, or entry points are identified in the issue. Start by mapping the existing issue-closing, achievement, profile/history, and sharing flows, then clarify the achievement model, reward sizes, and chat-sharing behavior before defining completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100