ended up with two chats, to the same user, with totally different threads.
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
@nobitagit and I have two duplicate chats. Each with different threads.
I think because I added him as a Github user, then invited him as a keybase user?
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 report names no files, tests, or entry points. Start by reproducing the duplicate-chat case after adding the same person through GitHub and Keybase, then trace the identity and chat creation paths; done means explaining why separate threads are created and covering the behavior with a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100