Keybase transport not allowed for git submodules
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've created a new git repo in keybase, and tried to add it as a submodule into a regular unencrypted repo.
Results:
fatal: transport 'keybase' not allowed
fatal: clone of 'keybase://team/organisation/reponame' into submodule path '/Users/user/organisation/unencrypted-repo/encrypted-repo' failed
Possibly out of scope or more of an issue for git itself, however I think it will be helpful to have an issue listed here for reference.
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 reported failure when adding a keybase://team/organisation/reponame repository as a submodule in an unencrypted repository. Check whether the rejection comes from Git's submodule transport handling or Keybase's integration; done means establishing a supported fix or documenting that the behavior belongs elsewhere.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100