Le 07/09/2015 19:59, Sean P. DeNigris a écrit :
Let's say you decide to port a repo from StHub to GitHub. Here's a logical workflow: 1. Create a repo via the GitHub we interface so you get a nice license file and readme 2. Create a MCFileTreeGitRemoteRepository as the destination for the port. For example: (cloneFolder / 'repository') ensureCreateDirectory. destination := MCFileTreeGitRemoteRepository location: 'git@github.com:seandenigris/Superuser.git' name: cloneFolder subdirectory: 'repository' branch: ''.
Oops! I couldn't find a magic incantation to get #2 to work. Here is what seems to be the problem: If you specify the 'repository' subdirectory, you get an error that it doesn't exist (because there's no way to autogenerate empty directories from the GitHub web interface), but if you create it before the clone, you get an error that the pre-existing cloneFolder is not a git repo. Catch 22!
It would be nice if GitFileTree cloned the repo and then created the subdirectory if needed. I hacked around a bit, but didn't get very far :/
Good point. It is doable with probably a single line (when opening the repository, ensure the target directory is created if it doesn't exist)
I ended up manually cloning and then creating a vanilla GitFileTree repo
This work-around allways exist ;) I'll try and add an auto-creation if the target repository is missing. Thierry
----- Cheers, Sean -- View this message in context: http://forum.world.st/GitFileTree-with-Project-Template-from-GitHub-tp484862... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.