create() in existing directory #627

Activity

1. gaborcsardi commented on Oct 27, 2014

   

   gaborcsardi

   on Oct 27, 2014

   Member

   More actions

   This is what I usually do:

   Rscript -e 'devtools::create("newpackage")'
   cd newpackage
   git init .
   git add .
   git commit -m 'Initial commit, after devtools::create()'
   ...

   This seems to be about the same amount of typing.
2. krlmlr commented on Oct 27, 2014

   

   krlmlr

   on Oct 27, 2014

   MemberAuthor

   More actions

   No doubt. It just hurts when you try to do it the other way round. Related: #593.
3. mbojan commented on Oct 28, 2014

   

   mbojan

   on Oct 28, 2014

   More actions

   I think it might be useful, e.g. if you clone an (almost) empty repository to create a package there. For example, when you clone a GitHub repository containing only README.md
4. hadley commented on Nov 5, 2014

   

   hadley

   on Nov 5, 2014

   Member

   More actions

   create() is designed to be a first step, not a second. I think you should either adopt the standard devtools workflow, or submit a PR that implements a new function (extracting out most of the code from create()).
5. hadley

   closed this as completedon Nov 5, 2014
6. krlmlr commented on Nov 5, 2014

   

   krlmlr

   on Nov 5, 2014

   MemberAuthor

   More actions

   Before submitting a PR, I wanted to hear opinions. Personally, I think that tools should adopt to workflows, not the other way round.

   I'd like to look further into this issue. What would be a good name for the new function?

   🎉React with 🎉1Reacted by John Sobanski
7. hadley

   added a commit that references this issue on Nov 5, 2014

   Merge pull request #637 from krlmlr/627-setup-package

   ...

   This issue will close once commit bd9c252 is merged into the 'main' branch.

   bd9c252
8. lock

   locked and limited conversation to collaborators on Sep 18, 2018