Git repository unusable after one of the user revoked a device
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Initializing Keybase... done.
git-remote-keybase error: (1) /keybase/team/xxx was last written by an unknown device claiming to belong to user xxx_prod. The device has possibly been revoked by the user. Use `keybase log send` to file an issue with the Keybase admins.
my log id: b06fe18d88f656aecc54061c
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 with the git-remote-keybase error shown in the report and the device-revocation behavior it describes. Use the provided log id with the Keybase admins as directed, then determine what evidence is needed to make the affected Git repository usable again after a device is revoked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, go
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100