Submitting bug reports
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
[Everything seems to be running smooth on here but am going to have to get better acquainted with terminal for key-base]
my log id: 0a06dc38957dacabf7ba541c
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 entry point is identified. First clarify what behavior is failing in Keybase and provide reproduction steps, including the terminal context and the log ID 0a06dc38957dacabf7ba541c. Done should be a confirmed, reproducible bug with a defined scope and an appropriate regression check.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100