clone command optional parameter for renaming of repo's name

[varemenos]

I have the following repositories [dotfiles, themes, apps, dev] but their repository names have a "castle-" prefix for namespacing reasons. What I wish I could do is the following:

$ homeshick clone user@somewhere/castle-dotfiles.git dotfiles

Which would take the castle-dotfiles directory and rename it to dotfiles (same as git's behavior, git clone user@somewhere/castle-dotfiles.git dotfiles)

[andsens]

I see the predicament, but homeshick allows you to pass multiple git urls to clone so you can bootstrap easily with homeshick clone tpope/vim-git robbyrussell/oh-my-zsh altercation/vim-colors-solarized etc.. Your suggestion would break that behavior.

However: Because homeshick has no config files and only works with whatever it sees in the filesystem, you can pretty easily just clone the castles with git and then run homeshick link. homeshick does not care about what the url of the upstream remote is, so you can just run:

git clone user@somewhere/castle-dotfiles.git $HOME/.homeshick/repos/dotfiles
homeshick link dotfiles

or

homeshick -b clone user@somewhere/castle-dotfiles.git
(cd $HOME/.homeshick/repos; mv castle-dotfiles dotfiles)
homeshick link dotfiles

[squaresurf]

I may be wrong, but wouldn't it be better to mimick git's functionality with this since homeshick is built on git and using a git term (clone)? What do you think about adding this functionality and moving the "bootstrap" feature of the clone command to a new bootstrap command?

[andsens]

Meh, homeshick isn't meant to mimick git, it's meant to wrap it, which I perceive as quite different.
I agree that clone is an unfortunate name for that command and that may be the real issue here.

I'll leave it be for now, because so far it has only been a minor hindrance for a single person. I won't change the established way of interacting with homeshick on that basis.