lumodon / lumodon/Issue-Distributor
Add controls for categorizing issues
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
pull issues out of normal flow when marked as difficult.
ability to mark issue as something YOU don't want to touch ever again. (but not necessarily a bad issue)
Eventually upgrade to use sockets to get immediate feedback if anyone pulled out.
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 file, test, or code entry point is identified in the issue; begin by locating the issue categorization and assignment flow. Define how difficult and declined issues affect distribution, and what completion means for the later socket-based feedback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100