* using log directory 'd:/Rcompile/CRANpkg/local/4.4/gitlabr.Rcheck' * using R version 4.4.0 RC (2024-04-16 r86468 ucrt) * using platform: x86_64-w64-mingw32 * R was compiled by gcc.exe (GCC) 13.2.0 GNU Fortran (GCC) 13.2.0 * running under: Windows Server 2022 x64 (build 20348) * using session charset: UTF-8 * checking for file 'gitlabr/DESCRIPTION' ... OK * this is package 'gitlabr' version '2.0.1' * package encoding: UTF-8 * checking package namespace information ... OK * checking package dependencies ... OK * checking if this is a source package ... OK * checking if there is a namespace ... OK * checking for hidden files and directories ... OK * checking for portable file names ... OK * checking whether package 'gitlabr' can be installed ... OK * checking installed package size ... OK * checking package directory ... OK * checking 'build' directory ... OK * checking DESCRIPTION meta-information ... OK * checking top-level files ... OK * checking for left-over files ... OK * checking index information ... OK * checking package subdirectories ... OK * checking code files for non-ASCII characters ... OK * checking R files for syntax errors ... OK * checking whether the package can be loaded ... [1s] OK * checking whether the package can be loaded with stated dependencies ... [1s] OK * checking whether the package can be unloaded cleanly ... [1s] OK * checking whether the namespace can be loaded with stated dependencies ... [1s] OK * checking whether the namespace can be unloaded cleanly ... [1s] OK * checking loading without being on the library search path ... [1s] OK * checking use of S3 registration ... OK * checking dependencies in R code ... OK * checking S3 generic/method consistency ... OK * checking replacement functions ... OK * checking foreign function calls ... OK * checking R code for possible problems ... [4s] OK * checking Rd files ... [1s] 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. | ^ * checking Rd metadata ... OK * checking Rd cross-references ... OK * checking for missing documentation entries ... OK * checking for code/documentation mismatches ... OK * checking Rd \usage sections ... OK * checking Rd contents ... OK * checking for unstated dependencies in examples ... OK * checking contents of 'data' directory ... OK * checking data for non-ASCII characters ... [0s] OK * checking LazyData ... OK * checking data for ASCII and uncompressed saves ... OK * checking installed files from 'inst/doc' ... OK * checking files in 'vignettes' ... OK * checking examples ... [3s] OK * checking for unstated dependencies in 'tests' ... OK * checking tests ... [1s] OK Running 'testthat.R' [1s] * checking for unstated dependencies in vignettes ... OK * checking package vignettes ... OK * checking re-building of vignette outputs ... [10s] OK * checking PDF version of manual ... [22s] OK * checking HTML version of manual ... [4s] OK * DONE Status: 1 NOTE