-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
createEmptyGithubRepo - the 'repoDir' argument #142
Comments
This may somehow lead to changes in |
First time when I used createEmptyGithubRepo I was quite surprised that the repo was created in the local directory. So if it is impossible then it is impossible, butI see that the agithub function can do the setwd() on the beginning and then again at the end (after creation of the github repository). |
@pbiecek I've added |
Correct me if I'm wrong, but here repoDir has different meaning than in if repoDir is missing then repoDir = repo and then you create a dir So it is not possible to create repo in the root of github repository but you will have always a directory with repo files in github repository. 2015-12-28 19:29 GMT+01:00 Marcin Kosiński notifications@github.com:
pozdrawiam serdecznie, |
Ok I think now it should be more clean (I've added a commit). Do you suggest changing the name to 2015-12-29 18:12 GMT+01:00 Przemysław Biecek notifications@github.com:
|
I do not think that a new argument's name is the best solution (it is a solution but adds some complexity). |
I think that createEmptyGithubRepo should take both repoName and repoDir arguments, to specify where is should be located on local disk and how it should be named at GitHub.
The text was updated successfully, but these errors were encountered: