GitHub Boards x Pins Authentication Deprecation

davisderodes · August 17, 2021, 4:03pm

Hi!

I received an email today from GitHub informing me that their PAT and client_id/client_secret methods of authentication are being deprecated.

Do pins::board_register_github(repo = "owner/repo") and board_register_github(repo = "owner/repo", token = "<new-token>") use this method of authentication? Given github is sending me an email about how I can't do this in the future, I'm assuming that's true.

Is there an existing workaround or is there a planned workaround for this authentication issue?

Thank you so much,
Davis

mara · August 18, 2021, 1:18pm

Pins uses whatever PAT you have in your environment, which should still work with the GitHub updates.

github.com

rstudio/pins/blob/bb8a9dbf33b77e36245812bc2e7019f08133993e/R/legacy_github.R

#' GitHub board (legacy API)
#'
#' To use a GitHub board, you'll need to set up authentication. This is likely
#' to just work if you already use GitHub for other purposes since pins will
#' inspect your  `GITHUB_PAT` environment variable. Otherwise, you can follow
#' the instructions at <https://happygitwithr.com/credential-caching.html> to
#' get set up.
#'
#' # Large Files
#'
#' A GitHub repo only supports files under 25MB in size (100MB in theory but
#' there is additional overhead when using the GitHub API). To store large
#' files, GitHub
#' [recommends](https://help.github.com/en/articles/distributing-large-binaries)
#' storing them using GitHub Releases which support up to 2GB files, which
#' is what pins uses. You don't need to do anything extra as this will happen
#' behind the scenes, but don't be surprised if pins creates releases in your
#' repo.
#'
#' @inheritParams new_board

This file has been truncated. show original

system · September 8, 2021, 1:18pm

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.

If you have a query related to it or one of the replies, start a new topic and refer back with a link.