create a remake.yml template

[aammd]

This is just to get the idea started here. A simple function that a use can call to add a remake.yml file to the current working directory.

Fixes #54.

[richfitz]

For some reason I don't see notifications on pull requests via email. You'd think that I would.

Don't worry about the failing check; it's appveyor for reasons that I don't really understand. I might just disable it until I can find the patience to work out what is really going on.

[richfitz]

This file does not exist - I presume you're trying to copy over this file? That file is not installed (only files below inst/ would be). Perhaps it would be better to install a new, heavily commented, file that is custom designed for being easy to start with?

[richfitz]

Can we get a test on this perhaps? This sort of testing is a total pain --- you'll probably have to run in a temporary directory like so:

test_that("whatever", {
  owd <- setwd(tempfile())
  on.exit(setwd(owd))
   ## ... tests go here.
})

Things to test for:

• remake file is actually copied over (does not exist before running, does exist after running)
• whatever remake file is copied over is valid (i.e. something like remake::list_targets() does not throw).
• use_remake will throw when it would overwrite (as you have implemented)
• Different dir paths work as expected
• Determine appropriate behaviour when dir does not exist yet (create, throw (how is the error message?))

[richfitz]

Also, possible things to add after dealing with the above (could be a subsequent PR if you'd rather)

• Support for a vector of packages, sources to propagate the appropriate fields
• Support for non-CRAN package sources to propagate the remake_sources.yml file (e.g., sources=list(remoji="richfitz/remoji")

[richfitz]

Hola @aammd - any interest in picking this up again?

[wlandau]

I like this approach for preexisting projects. Any chance we could do use_remake() for old projects and example_remake() (#100) for new ones?