CRAN Package Check Results for Package gitlabr

Last updated on 2024-03-28 17:49:29 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 2.0.1 5.15 63.60 68.75 NOTE
r-devel-linux-x86_64-debian-gcc 2.0.1 4.43 48.64 53.07 NOTE
r-devel-linux-x86_64-fedora-clang 2.0.1 90.58 NOTE
r-devel-linux-x86_64-fedora-gcc 2.0.1 98.90 NOTE
r-devel-windows-x86_64 2.0.1 8.00 74.00 82.00 NOTE
r-patched-linux-x86_64 2.0.1 6.96 62.66 69.62 NOTE
r-release-linux-x86_64 2.0.1 5.99 60.78 66.77 OK
r-release-macos-arm64 2.0.1 41.00 OK
r-release-macos-x86_64 2.0.1 58.00 OK
r-release-windows-x86_64 2.0.1 9.00 78.00 87.00 OK
r-oldrel-macos-arm64 2.0.1 29.00 OK
r-oldrel-windows-x86_64 2.0.1 9.00 79.00 88.00 OK

Check Details

Version: 2.0.1
Check: Rd files
Result: NOTE checkRd: (-1) gitlab.Rd:63: Lost braces; missing escapes or markup? 63 | This is {gitlabr}'s core function to talk to GitLab's server API via HTTP(S). Usually you will not | ^ checkRd: (-1) gitlab.Rd:64: Lost braces; missing escapes or markup? 64 | use this function directly too often, but either use {gitlabr}'s convenience wrappers or write your | ^ checkRd: (-1) gitlab.Rd:65: Lost braces; missing escapes or markup? 65 | own. See the {gitlabr} vignette for more information on this. | ^ checkRd: (-1) gitlab.Rd:45: Lost braces; missing escapes or markup? 45 | to prevent {gitlabr} getting stuck in retrieving an unexpectedly high number of entries (e.g. of a | ^ checkRd: (-1) gitlabr_0_7_renaming.Rd:6: Lost braces; missing escapes or markup? 6 | \title{renaming from {gitlabr} version 0.6.4 to 0.7} | ^ checkRd: (-1) gl_connection.Rd:31: Lost braces; missing escapes or markup? 31 | \item{api_location}{location of the GitLab API under the \code{gitlab_url}, usually and by default "/api/${api_version}/"} | ^ checkRd: (-1) gl_connection.Rd:57: Lost braces; missing escapes or markup? 57 | {gitlabr} since version 1.1.6. "v3" as a parameter value is not removed, since for many instances, {gitlabr} | ^ checkRd: (-1) gl_connection.Rd:57: Lost braces; missing escapes or markup? 57 | {gitlabr} since version 1.1.6. "v3" as a parameter value is not removed, since for many instances, {gitlabr} | ^ checkRd: (-1) gl_shiny_login.Rd:37: Lost braces 37 | \item{project}{if not NULL, a code{\link{gl_project_connection}} is created to this project} | ^ checkRd: (-1) use_gitlab_ci.Rd:39: Lost braces; missing escapes or markup? 39 | \item "check-coverage-pkgdown": Check package along with Code coverage with {covr} | ^ checkRd: (-1) use_gitlab_ci.Rd:40: Lost braces; missing escapes or markup? 40 | and {pkgdown} site on GitLab Pages | ^ checkRd: (-1) use_gitlab_ci.Rd:41: Lost braces; missing escapes or markup? 41 | \item "check-coverage-pkgdown-renv": Check package built in a fixed {renv} state | ^ checkRd: (-1) use_gitlab_ci.Rd:42: Lost braces; missing escapes or markup? 42 | along with Code coverage with {covr} and {pkgdown} site on GitLab Pages. | ^ checkRd: (-1) use_gitlab_ci.Rd:42: Lost braces; missing escapes or markup? 42 | along with Code coverage with {covr} and {pkgdown} site on GitLab Pages. | ^ checkRd: (-1) use_gitlab_ci.Rd:43: Lost braces; missing escapes or markup? 43 | \item "bookdown": Build {bookdown} HTML and PDF site on GitLab Pages | ^ checkRd: (-1) use_gitlab_ci.Rd:44: Lost braces; missing escapes or markup? 44 | \item "bookdown-production": Build {bookdown} HTML and PDF site on GitLab Pages. | ^ Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-x86_64, r-patched-linux-x86_64