Many URLs: http --> https

jennybc · jennybc · commit 144c66e00ae1 · 2019-07-03T22:24:59.000-07:00
diff --git a/.github/CODE_OF_CONDUCT.md b/.github/CODE_OF_CONDUCT.md
@@ -21,5 +21,5 @@ Instances of abusive, harassing, or otherwise unacceptable behavior may be repor
 opening an issue or contacting one or more of the project maintainers.
 
 This Code of Conduct is adapted from the Contributor Covenant 
-(http://contributor-covenant.org), version 1.0.0, available at 
-http://contributor-covenant.org/version/1/0/0/
+(https://contributor-covenant.org), version 1.0.0, available at 
+https://contributor-covenant.org/version/1/0/0/
diff --git a/NEWS.md b/NEWS.md
@@ -393,7 +393,7 @@ No longer in Imports: backports, httr, rematch2, rmarkdown (moved to Suggests),
 
 # usethis 1.3.0
 
-* usethis has a website: <http://usethis.r-lib.org> (#217). It includes an article with advice on system setup, for usethis and for R development more generally.
+* usethis has a website: <https://usethis.r-lib.org> (#217). It includes an article with advice on system setup, for usethis and for R development more generally.
 
 * `edit_*()` functions now return the target path, invisibly (#255).
 
@@ -431,7 +431,7 @@ No longer in Imports: backports, httr, rematch2, rmarkdown (moved to Suggests),
 
 * `use_blank_slate()` provides a way to opt in to an RStudio workflow where the user's workspace is neither saved nor reloaded between R sessions. Automated for `scope = "project"`. Provides UI instructions for `scope = "user"`, for now (#139).
 
-* `use_tidy_style()` styles an entire project according to <http://style.tidyverse.org> (#72, #197 @lorenzwalthert).
+* `use_tidy_style()` styles an entire project according to <https://style.tidyverse.org> (#72, #197 @lorenzwalthert).
 
 * GitHub conventions common to tidyverse packages are enacted by `use_tidy_contributing()`, `use_tidy_issue_template()`, and `use_tidy_support()` (@batpigandme, #143, #166).
 
diff --git a/R/badge.R b/R/badge.R
@@ -11,7 +11,7 @@
 #'
 #' * `use_badge()`: a general helper used in all badge functions
 #' * `use_bioc_badge()`: badge indicates [BioConductor build
-#' status](http://bioconductor.org/developers/)
+#' status](https://bioconductor.org/developers/)
 #' * `use_cran_badge()`: badge indicates what version of your package is
 #' available on CRAN, powered by <https://www.r-pkg.org>
 #' * `use_lifecycle_badge()`: badge declares the developmental stage of a
diff --git a/R/code-of-conduct.R b/R/code-of-conduct.R
@@ -4,8 +4,8 @@
 #' `.Rbuildignore`, in the case of a package. The goal of a code of conduct is
 #' to foster an environment of inclusiveness, and to explicitly discourage
 #' inappropriate behaviour. The template comes from
-#' <http://contributor-covenant.org>, version 1:
-#' <http://contributor-covenant.org/version/1/0/0/>.
+#' <https://contributor-covenant.org>, version 1:
+#' <https://contributor-covenant.org/version/1/0/0>.
 #'
 #' @param path Path of the directory to put `CODE_OF_CONDUCT.md` in, relative to
 #'   the active project. Passed along to [use_directory()]. Default is to locate
diff --git a/R/proj.R b/R/proj.R
@@ -99,7 +99,7 @@ proj_path <- function(..., ext = "") {
 }
 
 #' @describeIn proj_utils Runs code with a temporary active project. It is an
-#'   example of the `with_*()` functions in [withr](http://withr.r-lib.org).
+#'   example of the `with_*()` functions in [withr](https://withr.r-lib.org).
 #' @param code Code to run with temporary active project.
 #' @param quiet Whether to suppress user-facing messages, while operating in the
 #'   temporary active project.
@@ -122,7 +122,7 @@ with_project <- function(path = ".",
 #' @describeIn proj_utils Sets an active project until the current execution
 #'   environment goes out of scope, e.g. the end of the current function or
 #'   test.  It is an example of the `local_*()` functions in
-#'   [withr](http://withr.r-lib.org).
+#'   [withr](https://withr.r-lib.org).
 #' @param .local_envir The environment to use for scoping. Defaults to current
 #'   execution environment.
 #' @export
diff --git a/R/tidyverse.R b/R/tidyverse.R
@@ -23,7 +23,7 @@
 #'   programming with the tidy eval toolkit.
 #'
 #' * `use_tidy_style()`: styles source code according to the [tidyverse style
-#' guide](http://style.tidyverse.org). This function will overwrite files! See
+#' guide](https://style.tidyverse.org). This function will overwrite files! See
 #' below for usage advice.
 #'
 #' * `use_tidy_versions()`: pins all dependencies to require at least
@@ -47,9 +47,9 @@
 #' `use_tidy_coc()`.
 #'
 #' @section `use_tidy_style()`:
-#' Uses the [styler package](http://styler.r-lib.org) package to style all code
+#' Uses the [styler package](https://styler.r-lib.org) package to style all code
 #' in a package, project, or directory, according to the [tidyverse style
-#' guide](http://style.tidyverse.org).
+#' guide](https://style.tidyverse.org).
 #'
 #' **Warning:** This function will overwrite files! It is strongly suggested to
 #' only style files that are under version control or to first create a backup
diff --git a/inst/templates/tidy-contributing.md b/inst/templates/tidy-contributing.md
@@ -25,7 +25,7 @@ bug, create an associated issue and illustrate the bug with a minimal
 *  Look at the Travis and AppVeyor build status before and after making changes.
 The `README` should contain badges for any continuous integration services used
 by the package.  
-*  New code should follow the tidyverse [style guide](http://style.tidyverse.org).
+*  New code should follow the tidyverse [style guide](https://style.tidyverse.org).
 You can use the [styler](https://CRAN.R-project.org/package=styler) package to
 apply these styles, but please don't restyle code that has nothing to do with 
 your PR.  
diff --git a/man/badges.Rd b/man/badges.Rd
diff --git a/man/proj_utils.Rd b/man/proj_utils.Rd
diff --git a/man/tidyverse.Rd b/man/tidyverse.Rd
diff --git a/man/use_code_of_conduct.Rd b/man/use_code_of_conduct.Rd
diff --git a/vignettes/articles/usethis-setup.Rmd b/vignettes/articles/usethis-setup.Rmd
@@ -156,9 +156,9 @@ Substitute your preferred editor for emacs here. A popular choice is [nano](http
 
 As stated above, usethis doesn't actually use the Git you install and has no absolute requirement that you use GitHub or use RStudio. But use of usethis is highly correlated with the desire to do all of these things, in a pleasant way.
 
-If you plan to use GitHub, you need to make sure your local Git can pull from and push to GitHub.com. That is beyond the scope of this article, but see the [Connect to GitHub](http://happygitwithr.com/push-pull-github.html) section in Happy Git. You probably don't want to enter your username and password all the time, so either [cache credentials for HTTPS](http://happygitwithr.com/credential-caching.html) or [set up SSH keys](http://happygitwithr.com/ssh-keys.html). Then set the `usethis.protocol` option to match, i.e. to either "https" or "ssh". This setup makes functions like `usethis::use_github()` much easier to use.
+If you plan to use GitHub, you need to make sure your local Git can pull from and push to GitHub.com. That is beyond the scope of this article, but see the [Connect to GitHub](https://happygitwithr.com/push-pull-github.html) section in Happy Git. You probably don't want to enter your username and password all the time, so either [cache credentials for HTTPS](https://happygitwithr.com/credential-caching.html) or [set up SSH keys](https://happygitwithr.com/ssh-keys.html). Then set the `usethis.protocol` option to match, i.e. to either "https" or "ssh". This setup makes functions like `usethis::use_github()` much easier to use.
 
-If you want to use RStudio to work with Git (and therefore GitHub, see previous paragraph), you need to make sure RStudio can find your Git executable. This usually "just works". The [Connect RStudio to Git and GitHub](http://happygitwithr.com/rstudio-git-github.html) section of Happy Git helps you confirm that all is well. If all is not well, there are also [troubleshooting tips](http://happygitwithr.com/rstudio-see-git.html).
+If you want to use RStudio to work with Git (and therefore GitHub, see previous paragraph), you need to make sure RStudio can find your Git executable. This usually "just works". The [Connect RStudio to Git and GitHub](https://happygitwithr.com/rstudio-git-github.html) section of Happy Git helps you confirm that all is well. If all is not well, there are also [troubleshooting tips](https://happygitwithr.com/rstudio-see-git.html).
 
 ## Get and store a GitHub personal access token
 
