issue-submission sanity-check / without API key / process token
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16
- Forks
- 3
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 121
Description
User has perceived bug/feature/RFD but is not signed into Github API. They are about to go to the Github website and type something that may be redundant, because searching through all the various places is to much work. This feature would ask several questions about the bug to suggest a nice title, description, and format, intercept duplicates, and sign a credential resulting in a small token indicating that the process was followed.
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 names no files, tests, or entry points. Start by reviewing the CLI's existing GitHub issue-submission and authentication flow, then clarify the intended questions, duplicate detection, and token behavior. Done should include an agreed workflow and acceptance criteria for generating issue content and indicating that the process was followed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, rust
- Domain
- api, authentication, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100