install_gitlab: Install a package from GitLab

View source: R/install-gitlab.R

install_gitlabR Documentation

Install a package from GitLab


This function is vectorised on repo so you can install multiple packages in a single command. Like other remotes the repository will skip installation if force == FALSE (the default) and the remote state has not changed since the previous installation.


  subdir = NULL,
  auth_token = gitlab_pat(quiet),
  host = "",
  dependencies = NA,
  upgrade = c("default", "ask", "always", "never"),
  force = FALSE,
  quiet = FALSE,
  build = TRUE,
  build_opts = c("--no-resave-data", "--no-manual", "--no-build-vignettes"),
  build_manual = FALSE,
  build_vignettes = FALSE,
  repos = getOption("repos"),
  type = getOption("pkgType"),



Repository address in the format ⁠username/repo[@ref]⁠.


Subdirectory within repo that contains the R package.


To install from a private repo, generate a personal access token (PAT) with at least read_api scope in and supply to this argument. This is safer than using a password because you can easily delete a PAT without affecting any others. Defaults to the GITLAB_PAT environment variable.


GitLab API host to use. Override with your GitLab enterprise hostname, for example, "<PROTOCOL://>". The PROTOCOL is required by packrat during Posit Connect deployment. While install_gitlab may work without, omitting it generally leads to package restoration errors.


Which dependencies do you want to check? Can be a character vector (selecting from "Depends", "Imports", "LinkingTo", "Suggests", or "Enhances"), or a logical vector.

TRUE is shorthand for "Depends", "Imports", "LinkingTo" and "Suggests". NA is shorthand for "Depends", "Imports" and "LinkingTo" and is the default. FALSE is shorthand for no dependencies (i.e. just check this package, not its dependencies).

The value "soft" means the same as TRUE, "hard" means the same as NA.

You can also specify dependencies from one or more additional fields, common ones include:

  • Config/Needs/website - for dependencies used in building the pkgdown site.

  • Config/Needs/coverage for dependencies used in calculating test coverage.


Should package dependencies be upgraded? One of "default", "ask", "always", or "never". "default" respects the value of the R_REMOTES_UPGRADE environment variable if set, and falls back to "ask" if unset. "ask" prompts the user for which out of date packages to upgrade. For non-interactive sessions "ask" is equivalent to "always". TRUE and FALSE are also accepted and correspond to "always" and "never" respectively.


Force installation, even if the remote state has not changed since the previous install.


If TRUE, suppress output.


If TRUE build the package before installing.


Options to pass to ⁠R CMD build⁠, only used when build is TRUE.


If FALSE, don't build PDF manual ('–no-manual').


If FALSE, don't build package vignettes ('–no-build-vignettes').


A character vector giving repositories to use.


Type of package to update.


Other arguments passed on to utils::install.packages().

See Also

Other package installation: install_bioc(), install_bitbucket(), install_cran(), install_dev(), install_github(), install_git(), install_local(), install_svn(), install_url(), install_version()


## Not run: 

## End(Not run)

remotes documentation built on May 29, 2024, 7:51 a.m.