Skip to content
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

Use remotes directly rather than devtools #69

Closed
jimhester opened this issue Feb 12, 2019 · 2 comments
Closed

Use remotes directly rather than devtools #69

jimhester opened this issue Feb 12, 2019 · 2 comments
Labels
actions these are, well, actual actions (the building blocks) pkg-dev stuff to help other package developers

Comments

@jimhester
Copy link
Collaborator

While using docker container frees you from worrying about a lot of the dependency headaches of travis, you don't really need all of devtools installed.

Instead I would recommend using R CMD build to build the package, remotes to do the dependency installation, and if you want pretty check output the rcmdcheck package.

@maxheld83
Copy link
Owner

maxheld83 commented Feb 12, 2019

thanks @jimhester that's great advice.

I actually haven't thought through how to best use GitHub actions for packages yet; I just threw the main.workflow for this package together real quickly.

Hope to get to that soon, but I thought I'd start with the easier *down projects first.

Anyway, I'm very grateful for any advice or directions you might have for how to best leverage GitHub actions.

@maxheld83
Copy link
Owner

this is part of #2

@maxheld83 maxheld83 added pkg-dev stuff to help other package developers actions these are, well, actual actions (the building blocks) labels May 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
actions these are, well, actual actions (the building blocks) pkg-dev stuff to help other package developers
Projects
None yet
Development

No branches or pull requests

2 participants