-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Enable Github Action #3862
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
Enable Github Action #3862
Conversation
Phew, this seems really challenging... Currently I'm stuck with these issues:
|
Also @malcolmbarrett was working on this during the tidyverse dev day (https://github.com/malcolmbarrett/ggplot2/pull/1) you might want to pull in his changes here. |
Yes, let me know if I can help in any way. I got most of the way there, but I seemed to be stuck with latticeExtra having this new dep on R 3.6, which cascaded into the <3.6 builds. |
If the comment regarding latticeExtra relates to ggplot2, this is now fixed in master. |
Oh, great. I reran mine with upstream changes but it looks more or less the same as @yutannihilation's now. Since he's working on it, I'll close mine. If it's of use, here are the most recent GHA outputs. And the YAML I used:
|
Oh, sorry for taking your job @malcolmbarrett... I was wondering where is your working branch. Do you want to continue working on this? If so, I'll withdraw mine. |
This PR is ready for review now. |
@thomasp85 @clauswilke |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't judge the github actions parts, but the rest looks fine to me.
Thanks! @jimhester |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Actually... Will the new pkgdown action push dev versions to the main page? I'm still not completely clear on how this is handled? @jimhester can we have a pkgdown action that triggers when making a new GitHub release? |
Whether the built site will go to /dev/ or not is determined by the following rule of pkgdown; the GitHub Action is not related here. It just pushes what is built into gh-pages. https://pkgdown.r-lib.org/reference/build_site.html#development-mode |
It seems we can add this. May I add?
|
If we do we should also make sure that the pkgdown site is build based on the release, rather than current master |
Sure. |
You can have it run on published releases with the following on:
release:
types: published But maybe using the tag as @yutannihilation suggested would be an easier approach |
.github/workflows/R-CMD-check.yaml
Outdated
|
||
- name: Test coverage | ||
if: matrix.config.os == 'macOS-latest' && matrix.config.r == '3.6' | ||
run: covr::codecov(token = "${{secrets.CODECOV_TOKEN}}") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With latest version of covr and changes in codecov.io you no longer need a token here.
run: covr::codecov(token = "${{secrets.CODECOV_TOKEN}}") | |
run: covr::codecov() |
with the dev version of pkgdown you no longer need a token for pkgdown deploys, and with the latest CRAN covr you don't need a token for codecov.io results either, so this should be good to go once you change the codecov line. |
Wow, thanks for very useful advises! I didn't notice we are free from tokens now. Cool. |
I'm merging this in the hope that I'll have some time in the coming weeks so I can handle troubles related to this... Please file an issues if you find some strange behavior. |
Seems something is wrong with crandeps... I'll retry later.
|
The codecov service seems to have issues with HTTP 2 and projects with lots of data, e.g. ggplot2. Requiring HTTP 1.1 seems to fix the issue. Fixes tidyverse/ggplot2#3862
FWIW I get this same |
@jimhester Just curious,
do you mean you used your local macOS? If so, this might be a problem with LibreSSL bundled with macOS. This explains the difference that c.f. https://learnings.bolmaster2.com/posts/curl-openssl-tlsv1.3-on-macos.html Anyway, sticking with HTTP 1.1 seems a good idea considering those situations. |
Fix #3760, also fixes #3702.
Major changes
R CMD check
on Windows, macOS, and Ubuntu with the last 5 minor versions of R./document
will triggerdevtools::document()
automatically (example: Update autolayer.r yutannihilation/ggplot2#3 (comment)).Remove Travis and AppVeyor settingsStop building pkgdown site by Travis (Now I feel it's safe to leave them for now and remove when we confirm GitHub Actions CI does the right thing. But, pkgdown site should not be built twice, so I tweaked.travis.yml
only about this point)Diffs between the default YAML files are following:
Minor fixes
To enable these GitHub actions, I needed to do some tweaks
test-conditions.R
errors when it runs in covr, trying to parse a non-R script fileggplot2.rdb
. Addedpattern
argument tolist.files()
so that only R script files are parsed.test-geom-quantile.R
fails on Ubuntu with R >=3.4. This seems becauseall.equal.tbl_df()
doesn't accept tolerance (No tolerance in dplyr'sall.equal.tbl_df()
dplyr#2264). So, usedata.frame
instead oftibble
to compare them with tolerance.Test run
I tested this setting on my forked repo and confirmed they work. Note that
macOS-latest (3.6)
fails only because the token for codecov is not set yet.https://github.com/yutannihilation/ggplot2/actions/runs/51341080