Refresh the "double auth" roxygen template

Closes #1306

Author: jennybc

R/create.R

@@ -113,9 +113,10 @@ create_project <- function(path,
 #' [pr_init()], one of several [functions that work pull
 #' requests][pull-requests].
 #'
-#' `create_from_github()` works best when we can find a GitHub personal access
-#' token in the Git credential store (just like many other usethis functions).
-#' See [gh_token_help()] for more advice.
+#' `create_from_github()` works best when your GitHub credentials are
+#' discoverable. See below for more about authentication.
+#'
+#' @template double-auth
 #'
 #' @seealso
 #' * [use_github()] to go the opposite direction, i.e. create a GitHub repo
@@ -124,8 +125,6 @@ create_project <- function(path,
 #' * [use_course()] to download a snapshot of all files in a GitHub repo,
 #'   without the need for any local or remote Git operations
 #'
-#' @template double-auth
-#'
 #' @inheritParams create_package
 #' @param repo_spec A string identifying the GitHub repo in one of these forms:
 #'   * Plain `OWNER/REPO` spec

R/github.R

@@ -14,8 +14,8 @@
 #' * Configures `origin/DEFAULT` to be the upstream branch of the local
 #'   `DEFAULT` branch, e.g. `master` or `main`
 #'
-#' See the Authentication section below for general setup that is necessary for
-#' all of this to work.
+#' See below for the authentication setup that is necessary for all of this to
+#' work.
 #'
 #' @template double-auth
 #'

R/pr.R

@@ -25,24 +25,7 @@
 #' The `pr_*` functions also use your Git/GitHub credentials to carry out
 #' various remote operations. See below for more.
 #'
-#' @section Git/GitHub credentials:
-#' The `pr_*` functions interact with GitHub both as a conventional Git remote
-#' and via the REST API. Therefore, your credentials must be discoverable. Which
-#' credentials do we mean?
-#' * A GitHub personal access token (PAT) must be discoverable by the gh
-#'   package, which is used for GitHub operations via the REST API. See
-#'   [gh_token_help()] for more about getting and configuring a PAT.
-#' * If you use the HTTPS protocol for Git remotes, your PAT is also used for
-#'   Git operations, such as `git push`. Usethis uses the gert package for this,
-#'   so the PAT must be discoverable by gert. Generally gert and gh will
-#'   discover and use the same PAT. This ability to "kill two birds with one
-#'   stone" is why HTTPS + PAT is our recommended auth strategy for those new
-#'   to Git and GitHub and PRs.
-#' * If you use SSH remotes, your SSH keys must also be discoverable, in
-#'   addition to your PAT. The public key must be added to your GitHub account.
-#'
-#' Git/GitHub credential management is covered in a dedicated article:
-#' [Managing Git(Hub) Credentials](https://usethis.r-lib.org/articles/articles/git-credentials.html)
+#' @template double-auth
 #'
 #' @section For contributors:
 #' To contribute to a package, first use `create_from_github("OWNER/REPO")` to

man/create_from_github.Rd

@@ -1,40 +1,30 @@
-#' @section Authentication:
-#' This function potentially interacts with GitHub in two different ways:
-#' * via the GitHub REST API
-#' * as a conventional Git remote
-#'
-#' Therefore two types of auth happen.
-#'
+#' @section Git/GitHub Authentication:
 
-#' To create a new repo on GitHub, we **must** call the GitHub REST API, i.e.
-#' this isn't one of the standard remote Git operations. Therefore you must make
-#' a GitHub personal access token (PAT) available. See [gh_token_help()] for
-#' advice on getting and storing your token.
-#'
+#' Many usethis functions, including those documented here, potentially interact
+#' with GitHub in two different ways:
 
-#' When we clone or pull from GitHub or push to it, depending on the protocol
-#' (HTTPS vs. SSH) and the privacy of the repo, we may also need regular Git
-#' credentials, just like we'd need with command line Git.
-#'
-#' We highly recommend using the HTTPS protocol, unless you have a specific
-#' preference for SSH. If you are an "HTTPS person", your GitHub PAT (see above)
-#' can also be used to authorize standard Git remote operations. Therefore, once
-#' you've configured your PAT, your setup is complete!
+#' * Via the GitHub REST API. Examples: create a repo, a fork, or a pull
+#' request.
+
+#' * As a conventional Git remote. Examples: clone, fetch, or push.
 #'
 
-#' But what if you prefer the SSH protocol? usethis uses the gert package for
-#' Git operations and gert, in turn, relies on the credentials package for auth:
-#' * <https://docs.ropensci.org/gert/>
-#' * <https://docs.ropensci.org/credentials/>
+#' Therefore two types of auth can happen and your credentials must be
+#' discoverable. Which credentials do we mean?
 #'
 
-#' In usethis v2.0.0, we switched from git2r to gert + credentials. The main
-#' motivation is to provide a smoother user experience by discovering and using
-#' the same credentials as command line Git (and, therefore, the same as
-#' RStudio). The credentials package *should* automatically discover your SSH
-#' keys. This works so well that we have removed all credential-handling
-#' workarounds from usethis. If you have credential problems, focus your
-#' troubleshooting on getting the credentials package to find your SSH keys. Its
-#' [introductory
-#' vignette](https://docs.ropensci.org/credentials/articles/intro.html)
-#' is a good place to start.
+#' * A GitHub personal access token (PAT) must be discoverable by the gh
+#'   package, which is used for GitHub operations via the REST API. See
+#'   [gh_token_help()] for more about getting and configuring a PAT.
+
+#' * If you use the HTTPS protocol for Git remotes, your PAT is also used for
+#'   Git operations, such as `git push`. Usethis uses the gert package for this,
+#'   so the PAT must be discoverable by gert. Generally gert and gh will
+#'   discover and use the same PAT. This ability to "kill two birds with one
+#'   stone" is why HTTPS + PAT is our recommended auth strategy for those new
+#'   to Git and GitHub and PRs.
+#' * If you use SSH remotes, your SSH keys must also be discoverable, in
+#'   addition to your PAT. The public key must be added to your GitHub account.
+#'
+#' Git/GitHub credential management is covered in a dedicated article:
+#' [Managing Git(Hub) Credentials](https://usethis.r-lib.org/articles/articles/git-credentials.html)