RealDevSquad / RealDevSquad/Pulse-App
Analayse existing github issues for Triaging
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
We want to analyze our existing github issues across different RDS repos and do triaging
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 concerns analyzing existing GitHub issues across different RDS repositories, but it names no files, tests, entry points, or analysis criteria. Start by defining the repositories, triage fields, and expected output; done is not specified in the issue and needs agreement before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100