[pre-commit.ci] Fixing issues with pre-commit

Author: pre-commit-ci[bot]

.github/workflows/README.md

@@ -10,7 +10,7 @@ R console:
 
 ```r
 # Install/Update sandpaper
-options(repos = c(carpentries = "https://carpentries.r-universe.dev/", 
+options(repos = c(carpentries = "https://carpentries.r-universe.dev/",
   CRAN = "https://cloud.r-project.org"))
 install.packages("sandpaper")
 
@@ -42,13 +42,13 @@ This workflow does the following:
 
 #### Caching
 
-This workflow has two caches; one cache is for the lesson infrastructure and 
+This workflow has two caches; one cache is for the lesson infrastructure and
 the other is for the lesson dependencies if the lesson contains rendered
 content. These caches are invalidated by new versions of the infrastructure and
-the `renv.lock` file, respectively. If there is a problem with the cache, 
+the `renv.lock` file, respectively. If there is a problem with the cache,
 manual invaliation is necessary. You will need maintain access to the repository
 and you can either go to the actions tab and [click on the caches button to find
-and invalidate the failing cache](https://github.blog/changelog/2022-10-20-manage-caches-in-your-actions-workflows-from-web-interface/) 
+and invalidate the failing cache](https://github.blog/changelog/2022-10-20-manage-caches-in-your-actions-workflows-from-web-interface/)
 or by setting the `CACHE_VERSION` secret to the current date (which will
 invalidate all of the caches).
 
@@ -58,32 +58,32 @@ invalidate all of the caches).
 
 These workflows run on a schedule and at the maintainer's request. Because they
 create pull requests that update workflows/require the downstream actions to run,
-they need a special repository/organization secret token called 
-`SANDPAPER_WORKFLOW` and it must have the `public_repo` and `workflow` scope. 
+they need a special repository/organization secret token called
+`SANDPAPER_WORKFLOW` and it must have the `public_repo` and `workflow` scope.
 
 This can be an individual user token, OR it can be a trusted bot account. If you
 have a repository in one of the official Carpentries accounts, then you do not
 need to worry about this token being present because the Carpentries Core Team
 will take care of supplying this token.
 
-If you want to use your personal account: you can go to 
+If you want to use your personal account: you can go to
 <https://github.com/settings/tokens/new?scopes=public_repo,workflow&description=Sandpaper%20Token>
 to create a token. Once you have created your token, you should copy it to your
 clipboard and then go to your repository's settings > secrets > actions and
 create or edit the `SANDPAPER_WORKFLOW` secret, pasting in the generated token.
 
 If you do not specify your token correctly, the runs will not fail and they will
-give you instructions to provide the token for your repository. 
+give you instructions to provide the token for your repository.
 
 ### 02 Maintain: Update Workflow Files (update-workflow.yaml)
 
-The {sandpaper} repository was designed to do as much as possible to separate 
-the tools from the content. For local builds, this is absolutely true, but 
-there is a minor issue when it comes to workflow files: they must live inside 
-the repository. 
+The {sandpaper} repository was designed to do as much as possible to separate
+the tools from the content. For local builds, this is absolutely true, but
+there is a minor issue when it comes to workflow files: they must live inside
+the repository.
 
 This workflow ensures that the workflow files are up-to-date. The way it work is
-to download the update-workflows.sh script from GitHub and run it. The script 
+to download the update-workflows.sh script from GitHub and run it. The script
 will do the following:
 
 1. check the recorded version of sandpaper against the current version on github
@@ -100,25 +100,25 @@ This update is run weekly or on demand.
 
 For lessons that have generated content, we use {renv} to ensure that the output
 is stable. This is controlled by a single lockfile which documents the packages
-needed for the lesson and the version numbers. This workflow is skipped in 
+needed for the lesson and the version numbers. This workflow is skipped in
 lessons that do not have generated content.
 
 Because the lessons need to remain current with the package ecosystem, it's a
-good idea to make sure these packages can be updated periodically. The 
+good idea to make sure these packages can be updated periodically. The
 update cache workflow will do this by checking for updates, applying them in a
 branch called `updates/packages` and creating a pull request with _only the
-lockfile changed_. 
+lockfile changed_.
 
 From here, the markdown documents will be rebuilt and you can inspect what has
-changed based on how the packages have updated. 
+changed based on how the packages have updated.
 
 ## Pull Request and Review Management
 
 Because our lessons execute code, pull requests are a secruity risk for any
 lesson and thus have security measures associted with them. **Do not merge any
 pull requests that do not pass checks and do not have bots commented on them.**
 
-This series of workflows all go together and are described in the following 
+This series of workflows all go together and are described in the following
 diagram and the below sections:
 
 ![Graph representation of a pull request](https://carpentries.github.io/sandpaper/articles/img/pr-flow.dot.svg)
@@ -129,15 +129,15 @@ This workflow runs every time a pull request is created and its purpose is to
 validate that the pull request is okay to run. This means the following things:
 
 1. The pull request does not contain modified workflow files
-2. If the pull request contains modified workflow files, it does not contain 
+2. If the pull request contains modified workflow files, it does not contain
    modified content files (such as a situation where @carpentries-bot will
    make an automated pull request)
 3. The pull request does not contain an invalid commit hash (e.g. from a fork
    that was made before a lesson was transitioned from styles to use the
    workbench).
 
-Once the checks are finished, a comment is issued to the pull request, which 
-will allow maintainers to determine if it is safe to run the 
+Once the checks are finished, a comment is issued to the pull request, which
+will allow maintainers to determine if it is safe to run the
 "Receive Pull Request" workflow from new contributors.
 
 ### Receive Pull Request (pr-receive.yaml)
@@ -154,7 +154,7 @@ started.
 
 The first step of this workflow is to check if it is valid (e.g. that no
 workflow files have been modified). If there are workflow files that have been
-modified, a comment is made that indicates that the workflow is not run. If 
+modified, a comment is made that indicates that the workflow is not run. If
 both a workflow file and lesson content is modified, an error will occurr.
 
 The second step (if valid) is to build the generated content from the pull
@@ -164,7 +164,7 @@ request. This builds the content and uploads three artifacts:
 2. A summary of changes after the rendering process (diff)
 3. The rendered files (build)
 
-Because this workflow builds generated content, it follows the same general 
+Because this workflow builds generated content, it follows the same general
 process as the `sandpaper-main` workflow with the same caching mechanisms.
 
 The artifacts produced are used by the next workflow.
@@ -183,9 +183,9 @@ The steps in this workflow are:
 Importantly: if the pull request is invalid, the branch is not created so any
 malicious code is not published.
 
-From here, the maintainer can request changes from the author and eventually 
-either merge or reject the PR. When this happens, if the PR was valid, the 
-preview branch needs to be deleted. 
+From here, the maintainer can request changes from the author and eventually
+either merge or reject the PR. When this happens, if the PR was valid, the
+preview branch needs to be deleted.
 
 ### Send Close PR Signal (pr-close-signal.yaml)