4 ms·
You should be able to `sl clone ...` your git repo into a Sapling clone and use it that way, even if the repository is not on Github. I haven't personally trie
by durham_meta 4y ago
You should be able to `sl clone ...` your git repo into a Sapling clone and use it that way, even if the repository is not on Github. I haven't personally tried whether cloning like `sl clone /path/to/some/repo` works, but it should since we're actually using the actual git binary under the hood for clone, pull, and push.
- bentcorner 4y agoJust to clarify, I meant that I've already cloned it via git. Can I just start using sapling with it or do I need to delete the local repo and re-clone it with sapling?
- durham_meta 4y agoYou cannot just start using sl in a git repo. You need to make a Sapling clone of it. But you can make a Sapling clone of your local git repository, so you don't have to clone from the server again and you would get all your local work from your git repo. That might be the easiest way to try Sapling, so you don't have to delete your git checkout at all.
- achsvg 4y agoWhat's the command in sl to clone a local git repo? The documentation does not say anything about it...
- bentcorner 4y ago> But you can make a Sapling clone of your local git repository Whoa I didn't even know you could do that in git. I always considered clone to mean "download stuff from this location" but now it makes more sense. Thanks I'll give that a try.
- Vinnl 4y agoIs that a one-way street, or can I personally adopt Sapling for our Git repos without my collaborators even noticing? (For now.)
- durham_meta 4y agoYou could personally clone a git repo with Sapling and no one would know the difference. When using Sapling with a git repo, clone, push, and pull all use the actual git binary under the hood, so the server just sees git speaking to it.
- Vinnl 4y agoThat's great, looking forward to giving it a shot!