-
Notifications
You must be signed in to change notification settings - Fork 761
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
devtools::check
doesn't catch invalid file URIs
#2054
Comments
|
Got it. But how can I get rid of this |
Replace any internal links in your README with a full URL to GitHub (or perhaps a pkgdown site). |
That solved it! Thanks. I still think |
Like @jimhester said, |
Ah, got it. Sorry when he said it's a wrapper around I understand now why this is not possible. |
I am guessing for the same reason URL: https://cran.r-project.org/web/packages/ggstatsplot/readme/README.html
From: README.md
Status: 200
Message: OK
CRAN URL not in canonical form
URL: https://cran.r-project.org/web/packages/ggstatsplot/vignettes/
From: README.md
Status: 200
Message: OK
CRAN URL not in canonical form
The canonical URL of the CRAN page for a package is
https://CRAN.R-project.org/package=pkgname |
I you running check with |
Yes, this is the exact code I am running- devtools::check(
run_dont_test = TRUE,
manual = TRUE,
remote = TRUE,
incoming = TRUE,
force_suggests = TRUE
) |
This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue. https://reprex.tidyverse.org/ |
Although I had 0
NOTE
,ERROR
, orWARNING
on my local machine, this is theNOTE
I am getting with the development version of R (but not onR 3.6.0
).This is my
.Rbuildignore
for the R package in question-https://github.com/IndrajeetPatil/ggstatsplot/blob/master/.Rbuildignore
I am guessing this is a new check implemented on
R CMD CHECK
? Maybe worth including indevtools
as well?P.S. I am also attaching the full log in case you need to have a look it.
full_log.txt
The text was updated successfully, but these errors were encountered: