keybase / keybase/keybase-issues
github identity proof of never succeeded
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Github identity proof failed. I created new gist "keybase.md" and copied all the text from keybase "prove your github identity" saved in the github as a gist. When I click "Ok, I posted! check it" button. I am getting "Failed; retry?"
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 reproducing the GitHub identity proof flow with a newly created keybase.md gist and inspect why the “Failed; retry?” result occurs after clicking “Ok, I posted! check it”. Done means the proof succeeds for a correctly published gist, or the failure is narrowed to a specific validation problem.
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
- 25/100