-
Notifications
You must be signed in to change notification settings - Fork 8
Suggest we implement more gh-actions #71
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
Comments
@ryantibs @brookslogan Is it all right with you guys if I go ahead and implement this? There is the potential that 2 will run into cmu-delphi/epidatr#31 |
I'd say go for it---I haven't been following cmu-delphi/epidatr#31, so I think you're in a better position to judge this and how likely it is to run into problem, but sounds like you think it's worth it Apart from #69, worth implementing tests as in #42. I'm not sure where things stand on the testing front, but we should definitely get around to that ... |
So in this case would people |
The GitHub pages site is served by the On a push to This is actually a common setup. Running |
Currently only deploying to gh-pages. I suggest:
docs/
to thegh-pages
branch. Rebuild the docs automatically on push/merge.main
to prevent push/merge with failing code.For the automatic rebuilding, we likely should move some of the vignette data (maybe examples too) offline (as suggested in #69). This will generally make R-CMD-Check much faster.
The text was updated successfully, but these errors were encountered: