updated links in vignettes courtesy of urlchecker

vignettes/z-advanced-topic-reproducible-analytical-pipelines-with-nix.Rmd

@@ -87,7 +87,7 @@ packages, which is a package that is hosted on GitHub only with some data and
 useful functions for the project. Because it is on Github, it gets installed
 using the `buildRPackage` function from Nix. You can use this environment to
 work on you project, or to launch a `{targets}` pipeline. [This Github
-repository](https://github.com/ropensci/nix_targets_pipeline/tree/master)
+repository](https://github.com/b-rodrigues/nix_targets_pipeline/tree/master)
 contains the finalized project.
 
 On your local machine, you could execute the pipeline in the environment by
@@ -126,7 +126,7 @@ pipeline run automatically on GitHub Actions. The GitHub repository linked above
 has such a file, so each time changes get pushed, the pipeline runs on Github
 Actions and the results are automatically pushed to a branch called
 `targets-runs`. See the workflow file
-[here](https://github.com/ropensci/nix_targets_pipeline/blob/master/.github/workflows/run-pipeline.yaml).
+[here](https://github.com/b-rodrigues/nix_targets_pipeline/blob/master/.github/workflows/run-pipeline.yaml).
 This feature is very heavily inspired and adapted from the
 `targets::github_actions()` function.
 

vignettes/z-binary_cache.Rmd

@@ -134,5 +134,5 @@ NixOS's public cache, our `rstats-on-nix` cache, and your own, so your cache
 will only end up holding the binaries not found in the other two caches!
 
 Take a look at
-[this package’s](https://github.com/ropensci/rix/blob/main/.github/workflows/cachix_dev_env.yml)
+[this package’s](https://github.com/ropensci/rix/blob/main/.github/workflows/cachix-dev-env.yml)
 repository for an example of how this is done in practice.

vignettes/z-contributing_to_nixpkgs.Rmd

@@ -91,7 +91,7 @@ From there, you can see that `{AIUQ}`'s build failed because of another package,
 You can look for `{SuperGauss}` in the "Still failing jobs" tab, and see why
 `{SuperGauss}` failed, or you could check out a little dashboard I built that
 you can find
-[here](https://raw.githack.com/ropensci/nixpkgs-r-updates-fails/targets-runs/output/r-updates-fails.html).
+[here](https://raw.githack.com/b-rodrigues/nixpkgs-r-updates-fails/targets-runs/output/r-updates-fails.html).
 This dashboard shows essentially the same information you find on the "Still
 failing jobs" tab from before, but with several added niceties. First of all,
 there's a column called `fails_because_of` that shows the name of the package