Aaron Peikert

Hey Rachel, it sounds like you did everything flawlessly! `repro` checks under the hood with: ``` r repro:::has_github_token_ #> function()gh::gh_token() != "" #> #> ``` Created on 2021-03-26 by the...

Hi Mohammad, this is on me :disappointed: lots of people have had problems with the ssh setup. Try: ``` r repro::check_github() #> ✓ You and GitHub are on good terms,...

I hope that I may convince you (@cjvanlissa) to automatically include a `Makefile` (because the strict structure of a `worcs` project allows to infer this). Whether a user actually makes...

Great! My idea was to use `worcs::load_data()` and write it to a data file. But I have to admit that I don't know from the top of my head how...

I don't know how you feel, but I love opinionated solutions, till I hate that they restrict me somewhere were it hurts. I think of `worcs` as the opinionated version...

BTW I wrote it like that: https://github.com/aaronpeikert/repro/blob/66a8c07221b0802c19fd7f170c7235db51b0777b/R/automate.R#L196-L201 So users may use any read* command they like.

I am hesitant with the guessing (but could imagine using [`rio::import()`](https://github.com/leeper/rio) for the guessing), but I like the idea of storing it, how would you integrate it in the metadata...

I would generally be very interested in hearing your ideas about how to integrate your automated data workflow into this metadata (closed, open, synthetic).

But you have it a csv right? So a YAML counterpart would look like: ``` repro: data: mtcars.csv: checksum: "aslödfjasdlk" synthetic: mtcars_synth.csv read_fun: readr::read_csv write_fun: readr::write_csv ```

Not really pretty, but as everything is optional it might be a good solution.