Creating a subteam in a subteam wants to create the subteam in team instead.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Keybase GUI Version: 1.0.48-20180509161133+f6cd875742
Using the GUI within team.sub1 to create a subteam team.sub1.sub2 wants to create it as team.sub2 instead. There appears to be no way to create a subsubteam in the GUI.
It works using the CLI though: keybase team create team.sub1.sub2
Also, using the GUI within team.sub1.sub2 to create a sub3 subsubsubteam wants to create it as team.sub1.sub3 instead of team.sub1.sub2.sub3, there appears to be some -1 level mismatch.
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 GUI flow from team.sub1 and team.sub1.sub2, then compare its team-name handling with the CLI entry point keybase team create team.sub1.sub2. Done means the GUI creates each requested nested subteam at the full intended path, matching the CLI behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100