Github proof failed
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I know it's likely it's my fault but in case it's a bug.
Link to proof.
https://gist.github.com/Robloxxx/4cfc7a3a4d6779c8cf0e3ecb97bdaeca
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
Start by reviewing the linked GitHub proof in the issue and the Keybase client context; no source files or tests are named. Reproduce the reported proof failure and determine whether it is a client bug, with the cause and a verifiable fix or regression test marking the work done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100