Skip to content

create_tidy_package() to create public package with tidyverse/r-lib convensions #461

Closed

Description

@gaborcsardi

I am not sure if this is possible to do in one go, as the user might need to edit files, or maybe run git between the steps, we'll see. Order might change later.

  1. create_package()
  2. use_tidy_description()
  3. Add empty R/package.R file
  4. use_git()
  5. use_github()
  6. use_testthat()
  7. Add empty tests/testthat/test.R file.
  8. use_mit_license()
  9. use_readme_rmd()
  10. use_news_md()
  11. use_tidy_ci()
  12. use_appveyor()
  13. use_tidy_contributing()
  14. use_tidy_coc()
  15. use_lifecycle_badge()
  16. use_roxygen_md()
  17. use_cran_badge()
  18. use_coverage()
  19. Knit README.md
  20. Add all newly created files to git, commit, push.

The badges can be part of some use_tidy_readme_rmd(), because currently they need manual copy and paste.

Activity

  1. gaborcsardi commented on Sep 12, 2018

    @gaborcsardi
    MemberAuthor

    Just tried it, mostly works. Some steps are manual, we can fix that with a tidy README.Rmd template.

  2. jennybc commented on Sep 12, 2018

    @jennybc
    Member

    I think this might be best as a "doctor" or reporting function, i.e. it reports how much of this has been done and reminds of relevant functions for the un-done parts.

  3. gaborcsardi commented on Sep 12, 2018

    @gaborcsardi
    MemberAuthor

    That would be great as well, but I would very much like a version that just did everything....

  4. hadley commented on Sep 12, 2018

    @hadley
    Member

    I guess I tend to run them more over time - i.e. I don't run use_test() until I write the first test, and I don't run use_news_md() until after the first release. But I don't have any objection to setting up from the very beginning.

  5. jennybc commented on Sep 12, 2018

    @jennybc
    Member

    Perhaps the point is that is should be very resilient to re-application, i.e. it does something sensible de novo but can also cope when the work is partially done.

  6. hadley commented on Sep 12, 2018

    @hadley
    Member

    Yeah, and ideally you should be able to run it on a package that you created two years ago and bring it up to spec for today.

  7. gaborcsardi commented on Sep 12, 2018

    @gaborcsardi
    MemberAuthor

    Yeah, some things you can do on demand, like tests. But others I just tend to forget sometimes...

  8. added
    featurea feature request or enhancement
    tidy ✨tools for the tidyverse team
    on Nov 24, 2018
  9. hadley commented on Nov 24, 2018

    @hadley
    Member

    See also the checklist: tidyverse/readxl#241 (comment)

  10. hadley commented on Nov 29, 2018

    @hadley
    Member

    I think we need two pieces:

    • create_tidy_package() which calls create_package() and then the functions listed above

    • use_tidy_standards(cur = "1.0.0") which would create an issue checklist with the new functions you need to run.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    featurea feature request or enhancementtidy ✨tools for the tidyverse team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions