/devtools

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

make 'devtools::create()', 'devtools::setup()' more flexible #966

Closed
kevinushey opened this Issue Nov 3, 2015 · 3 comments

Comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@kevinushey @hadley
@kevinushey
Contributor

kevinushey commented Nov 3, 2015

I find myself doing something like this often:

  1. Create a new project in RStudio (but forget to create it as an R package),
  2. Wish that I could call devtools::create() or devtools::setup() to turn it into an R package.

Two things to 'wish' for:

  1. devtools::create() shouldn't fail for empty directories (or directories only a .Rproj file),
  2. devtools::setup() shouldn't fail if a .Rproj file already exists.
@hadley

This comment has been minimized.

Sign in to view
Member

hadley commented Jan 12, 2016

Any interest in implementing this?
@kevinushey

This comment has been minimized.

Sign in to view
Contributor

kevinushey commented Jan 12, 2016

Sure, I can take a shot at this.

kevinushey added a commit to kevinushey/devtools that referenced this issue Jan 12, 2016

@kevinushey
make 'create', 'setup' more flexible (closes r-lib#966) 
- 'devtools::create()' works when supplied an empty directory,
- 'devtools::setup()' no longer 'stop()'s when a .Rproj file
  already exists
f80196e

@hadley hadley closed this in ec7bd25 Jan 20, 2016

@lock

This comment has been minimized.

Sign in to view

lock bot commented Sep 18, 2018

This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue. https://reprex.tidyverse.org/

@lock lock bot locked and limited conversation to collaborators Sep 18, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.