Giter VIP home page Giter VIP logo

dotgithubfiles's Introduction

rOpenSci .github files

These templates are part of our guidance for package authors. Cf our gitbook in particular the chapter about collaboration.

Includes:

How to use the templates:

You can use the rodev::use_ro_github() function of rodev to perform all three steps at once, or

  • Put the content of dotgithub folder i.e. these three files in a .github directory in the base of your R package.
  • Update the CONTRIBUTING.md file with the package name.
  • Make sure to add a line with .github in your .Rbuildignore file in your package as well. E.g. run usethis::use_build_ignore(".github").

For more info on template files for GitHub repos:

Note: These files are mostly not specific to rOpenSci - there are a few items in the files specific to rOpenSci, but can be easily removed.

dotgithubfiles's People

Contributors

maelle avatar sckott avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

dotgithubfiles's Issues

what about r-lib verse

As @jennybc mentioned in ropensci/software-review-meta#13, sounds like devtools etc will soon be providinguse_ functions to create some of this? Obviously we can create our own as necessary, but for some of these maybe better to coordinate first with those efforts? I dunno, but I'm all for shared / common practices and fewer things we have to maintain independently... Perhaps @jennybc can weigh in more insightfully.

reorganize the files

since the 3 main files in this repo are not meant for targeting this repo itself, probably makes sense to put them in a folder, not named .github, but something else (e.g. dotgithub or so)

update the templates before inclusion in rodev

  • Make a PR to this repo with new versions of the templates
  • Put them in a dotgithub folder cf #3
  • Use them in a rodev helper function (because usethis templating functions mentioned in #4 don't exist yet I think?)
  • Mention the templates and function in dev_guide

quick comments re Contributing

Should the README or something note that Contributing is specific to ropensci? (it isn't really, other than the link to our discourse page, which means some people might adopt it with non-ropensci packages).

Should contributors be encouraged to file an issue discussing the proposed PR first? (excepting PRs to fix such things as documentation)?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.