From b71e2dd3608740162abe5bcda500480bf7076f6b Mon Sep 17 00:00:00 2001 From: SaranjeetKaur Date: Fri, 20 Feb 2026 10:32:34 +0000 Subject: [PATCH 1/2] Update workflows --- .github/workflows/README.md | 54 ++++++++++---------- .github/workflows/pr-close-signal.yaml | 3 +- .github/workflows/pr-comment.yaml | 21 ++++---- .github/workflows/pr-post-remove-branch.yaml | 4 +- .github/workflows/pr-preflight.yaml | 6 ++- .github/workflows/pr-receive.yaml | 3 +- .github/workflows/sandpaper-main.yaml | 9 ++-- .github/workflows/sandpaper-version.txt | 2 +- .github/workflows/update-cache.yaml | 7 +-- .github/workflows/update-workflows.yaml | 8 +-- 10 files changed, 62 insertions(+), 55 deletions(-) diff --git a/.github/workflows/README.md b/.github/workflows/README.md index 40d28931..18ab7650 100644 --- a/.github/workflows/README.md +++ b/.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 -the other is for the the lesson dependencies if the lesson contains rendered +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 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,17 +100,17 @@ 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 @@ -118,7 +118,7 @@ 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) diff --git a/.github/workflows/pr-close-signal.yaml b/.github/workflows/pr-close-signal.yaml index 3268909b..b1303c26 100644 --- a/.github/workflows/pr-close-signal.yaml +++ b/.github/workflows/pr-close-signal.yaml @@ -2,7 +2,8 @@ name: "Bot: Send Close Pull Request Signal" on: pull_request: - types: [closed] + types: + [closed] jobs: send-close-signal: diff --git a/.github/workflows/pr-comment.yaml b/.github/workflows/pr-comment.yaml index c4983cf1..f80d9d0c 100644 --- a/.github/workflows/pr-comment.yaml +++ b/.github/workflows/pr-comment.yaml @@ -12,6 +12,7 @@ concurrency: group: pr-${{ github.event.workflow_run.pull_requests[0].number }} cancel-in-progress: true + jobs: # Pull requests are valid if: # - they match the sha of the workflow run head commit @@ -29,12 +30,12 @@ jobs: number: ${{ steps.get-pr.outputs.NUM }} msg: ${{ steps.check-pr.outputs.MSG }} steps: - - name: "Download PR artifact" + - name: 'Download PR artifact' id: dl uses: carpentries/actions/download-workflow-artifact@main with: run: ${{ github.event.workflow_run.id }} - name: "pr" + name: 'pr' - name: "Get PR Number" if: ${{ steps.dl.outputs.success == 'true' }} @@ -80,19 +81,19 @@ jobs: permissions: contents: write steps: - - name: "Checkout md outputs" + - name: 'Checkout md outputs' uses: actions/checkout@v4 with: ref: md-outputs path: built fetch-depth: 1 - - name: "Download built markdown" + - name: 'Download built markdown' id: dl uses: carpentries/actions/download-workflow-artifact@main with: run: ${{ github.event.workflow_run.id }} - name: "built" + name: 'built' - if: ${{ steps.dl.outputs.success == 'true' }} run: unzip built.zip @@ -126,12 +127,12 @@ jobs: permissions: pull-requests: write steps: - - name: "Download comment artifact" + - name: 'Download comment artifact' id: dl uses: carpentries/actions/download-workflow-artifact@main with: run: ${{ github.event.workflow_run.id }} - name: "diff" + name: 'diff' - if: ${{ steps.dl.outputs.success == 'true' }} run: unzip ${{ github.workspace }}/diff.zip @@ -157,14 +158,14 @@ jobs: permissions: pull-requests: write steps: - - name: "Check for spoofing" + - name: 'Check for spoofing' id: dl uses: carpentries/actions/download-workflow-artifact@main with: run: ${{ github.event.workflow_run.id }} - name: "built" + name: 'built' - - name: "Alert if spoofed" + - name: 'Alert if spoofed' id: spoof if: ${{ steps.dl.outputs.success == 'true' }} run: | diff --git a/.github/workflows/pr-post-remove-branch.yaml b/.github/workflows/pr-post-remove-branch.yaml index 1f8dd158..9419e2be 100644 --- a/.github/workflows/pr-post-remove-branch.yaml +++ b/.github/workflows/pr-post-remove-branch.yaml @@ -16,7 +16,7 @@ jobs: permissions: contents: write steps: - - name: "Download artifact" + - name: 'Download artifact' uses: carpentries/actions/download-workflow-artifact@main with: run: ${{ github.event.workflow_run.id }} @@ -26,7 +26,7 @@ jobs: run: | unzip pr.zip echo "NUM=$(<./NUM)" >> $GITHUB_OUTPUT - - name: "Remove branch" + - name: 'Remove branch' uses: carpentries/actions/remove-branch@main with: pr: ${{ steps.get-pr.outputs.NUM }} diff --git a/.github/workflows/pr-preflight.yaml b/.github/workflows/pr-preflight.yaml index fcd098ab..34ad7aed 100644 --- a/.github/workflows/pr-preflight.yaml +++ b/.github/workflows/pr-preflight.yaml @@ -2,8 +2,10 @@ name: "Pull Request Preflight Check" on: pull_request_target: - branches: ["main"] - types: ["opened", "synchronize", "reopened"] + branches: + ["main"] + types: + ["opened", "synchronize", "reopened"] jobs: test-pr: diff --git a/.github/workflows/pr-receive.yaml b/.github/workflows/pr-receive.yaml index 29133281..7fbff6cd 100644 --- a/.github/workflows/pr-receive.yaml +++ b/.github/workflows/pr-receive.yaml @@ -2,7 +2,8 @@ name: "Receive Pull Request" on: pull_request: - types: [opened, synchronize, reopened] + types: + [opened, synchronize, reopened] concurrency: group: ${{ github.ref }} diff --git a/.github/workflows/sandpaper-main.yaml b/.github/workflows/sandpaper-main.yaml index 6ba03599..b3d1de8c 100644 --- a/.github/workflows/sandpaper-main.yaml +++ b/.github/workflows/sandpaper-main.yaml @@ -6,15 +6,15 @@ on: - main - master schedule: - - cron: "0 0 * * 2" + - cron: '0 0 * * 2' workflow_dispatch: inputs: name: - description: "Who triggered this build?" + description: 'Who triggered this build?' required: true - default: "Maintainer (via GitHub)" + default: 'Maintainer (via GitHub)' reset: - description: "Reset cached markdown files" + description: 'Reset cached markdown files' required: false default: false type: boolean @@ -33,6 +33,7 @@ jobs: GITHUB_PAT: ${{ secrets.GITHUB_TOKEN }} RENV_PATHS_ROOT: ~/.local/share/renv/ steps: + - name: "Checkout Lesson" uses: actions/checkout@v4 diff --git a/.github/workflows/sandpaper-version.txt b/.github/workflows/sandpaper-version.txt index 084c7bd0..c4195b90 100644 --- a/.github/workflows/sandpaper-version.txt +++ b/.github/workflows/sandpaper-version.txt @@ -1 +1 @@ -0.16.10 +0.17.2.9000 diff --git a/.github/workflows/update-cache.yaml b/.github/workflows/update-cache.yaml index f314f29d..a011c0c0 100644 --- a/.github/workflows/update-cache.yaml +++ b/.github/workflows/update-cache.yaml @@ -4,12 +4,12 @@ on: workflow_dispatch: inputs: name: - description: "Who triggered this build (enter github username to tag yourself)?" + description: 'Who triggered this build (enter github username to tag yourself)?' required: true - default: "monthly run" + default: 'monthly run' schedule: # Run every tuesday - - cron: "0 0 * * 2" + - cron: '0 0 * * 2' jobs: preflight: @@ -74,6 +74,7 @@ jobs: GITHUB_PAT: ${{ secrets.GITHUB_TOKEN }} RENV_PATHS_ROOT: ~/.local/share/renv/ steps: + - name: "Checkout Lesson" uses: actions/checkout@v4 diff --git a/.github/workflows/update-workflows.yaml b/.github/workflows/update-workflows.yaml index 9b53f82d..6414cf28 100644 --- a/.github/workflows/update-workflows.yaml +++ b/.github/workflows/update-workflows.yaml @@ -4,16 +4,16 @@ on: workflow_dispatch: inputs: name: - description: "Who triggered this build (enter github username to tag yourself)?" + description: 'Who triggered this build (enter github username to tag yourself)?' required: true - default: "weekly run" + default: 'weekly run' clean: description: 'Workflow files/file extensions to clean (no wildcards, enter "" for none)' required: false - default: ".yaml" + default: '.yaml' schedule: # Run every Tuesday - - cron: "0 0 * * 2" + - cron: '0 0 * * 2' jobs: check_token: From b88b0dd317d045854b99c37d61bc7d029cd3615f Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Fri, 20 Feb 2026 10:43:29 +0000 Subject: [PATCH 2/2] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- .github/workflows/README.md | 52 ++++++++++---------- .github/workflows/pr-close-signal.yaml | 3 +- .github/workflows/pr-comment.yaml | 21 ++++---- .github/workflows/pr-post-remove-branch.yaml | 4 +- .github/workflows/pr-preflight.yaml | 6 +-- .github/workflows/pr-receive.yaml | 3 +- .github/workflows/sandpaper-main.yaml | 9 ++-- .github/workflows/update-cache.yaml | 7 ++- .github/workflows/update-workflows.yaml | 8 +-- 9 files changed, 53 insertions(+), 60 deletions(-) diff --git a/.github/workflows/README.md b/.github/workflows/README.md index 18ab7650..3f55086e 100644 --- a/.github/workflows/README.md +++ b/.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 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,17 +100,17 @@ 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 @@ -118,7 +118,7 @@ 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) diff --git a/.github/workflows/pr-close-signal.yaml b/.github/workflows/pr-close-signal.yaml index b1303c26..3268909b 100644 --- a/.github/workflows/pr-close-signal.yaml +++ b/.github/workflows/pr-close-signal.yaml @@ -2,8 +2,7 @@ name: "Bot: Send Close Pull Request Signal" on: pull_request: - types: - [closed] + types: [closed] jobs: send-close-signal: diff --git a/.github/workflows/pr-comment.yaml b/.github/workflows/pr-comment.yaml index f80d9d0c..c4983cf1 100644 --- a/.github/workflows/pr-comment.yaml +++ b/.github/workflows/pr-comment.yaml @@ -12,7 +12,6 @@ concurrency: group: pr-${{ github.event.workflow_run.pull_requests[0].number }} cancel-in-progress: true - jobs: # Pull requests are valid if: # - they match the sha of the workflow run head commit @@ -30,12 +29,12 @@ jobs: number: ${{ steps.get-pr.outputs.NUM }} msg: ${{ steps.check-pr.outputs.MSG }} steps: - - name: 'Download PR artifact' + - name: "Download PR artifact" id: dl uses: carpentries/actions/download-workflow-artifact@main with: run: ${{ github.event.workflow_run.id }} - name: 'pr' + name: "pr" - name: "Get PR Number" if: ${{ steps.dl.outputs.success == 'true' }} @@ -81,19 +80,19 @@ jobs: permissions: contents: write steps: - - name: 'Checkout md outputs' + - name: "Checkout md outputs" uses: actions/checkout@v4 with: ref: md-outputs path: built fetch-depth: 1 - - name: 'Download built markdown' + - name: "Download built markdown" id: dl uses: carpentries/actions/download-workflow-artifact@main with: run: ${{ github.event.workflow_run.id }} - name: 'built' + name: "built" - if: ${{ steps.dl.outputs.success == 'true' }} run: unzip built.zip @@ -127,12 +126,12 @@ jobs: permissions: pull-requests: write steps: - - name: 'Download comment artifact' + - name: "Download comment artifact" id: dl uses: carpentries/actions/download-workflow-artifact@main with: run: ${{ github.event.workflow_run.id }} - name: 'diff' + name: "diff" - if: ${{ steps.dl.outputs.success == 'true' }} run: unzip ${{ github.workspace }}/diff.zip @@ -158,14 +157,14 @@ jobs: permissions: pull-requests: write steps: - - name: 'Check for spoofing' + - name: "Check for spoofing" id: dl uses: carpentries/actions/download-workflow-artifact@main with: run: ${{ github.event.workflow_run.id }} - name: 'built' + name: "built" - - name: 'Alert if spoofed' + - name: "Alert if spoofed" id: spoof if: ${{ steps.dl.outputs.success == 'true' }} run: | diff --git a/.github/workflows/pr-post-remove-branch.yaml b/.github/workflows/pr-post-remove-branch.yaml index 9419e2be..1f8dd158 100644 --- a/.github/workflows/pr-post-remove-branch.yaml +++ b/.github/workflows/pr-post-remove-branch.yaml @@ -16,7 +16,7 @@ jobs: permissions: contents: write steps: - - name: 'Download artifact' + - name: "Download artifact" uses: carpentries/actions/download-workflow-artifact@main with: run: ${{ github.event.workflow_run.id }} @@ -26,7 +26,7 @@ jobs: run: | unzip pr.zip echo "NUM=$(<./NUM)" >> $GITHUB_OUTPUT - - name: 'Remove branch' + - name: "Remove branch" uses: carpentries/actions/remove-branch@main with: pr: ${{ steps.get-pr.outputs.NUM }} diff --git a/.github/workflows/pr-preflight.yaml b/.github/workflows/pr-preflight.yaml index 34ad7aed..fcd098ab 100644 --- a/.github/workflows/pr-preflight.yaml +++ b/.github/workflows/pr-preflight.yaml @@ -2,10 +2,8 @@ name: "Pull Request Preflight Check" on: pull_request_target: - branches: - ["main"] - types: - ["opened", "synchronize", "reopened"] + branches: ["main"] + types: ["opened", "synchronize", "reopened"] jobs: test-pr: diff --git a/.github/workflows/pr-receive.yaml b/.github/workflows/pr-receive.yaml index 7fbff6cd..29133281 100644 --- a/.github/workflows/pr-receive.yaml +++ b/.github/workflows/pr-receive.yaml @@ -2,8 +2,7 @@ name: "Receive Pull Request" on: pull_request: - types: - [opened, synchronize, reopened] + types: [opened, synchronize, reopened] concurrency: group: ${{ github.ref }} diff --git a/.github/workflows/sandpaper-main.yaml b/.github/workflows/sandpaper-main.yaml index b3d1de8c..6ba03599 100644 --- a/.github/workflows/sandpaper-main.yaml +++ b/.github/workflows/sandpaper-main.yaml @@ -6,15 +6,15 @@ on: - main - master schedule: - - cron: '0 0 * * 2' + - cron: "0 0 * * 2" workflow_dispatch: inputs: name: - description: 'Who triggered this build?' + description: "Who triggered this build?" required: true - default: 'Maintainer (via GitHub)' + default: "Maintainer (via GitHub)" reset: - description: 'Reset cached markdown files' + description: "Reset cached markdown files" required: false default: false type: boolean @@ -33,7 +33,6 @@ jobs: GITHUB_PAT: ${{ secrets.GITHUB_TOKEN }} RENV_PATHS_ROOT: ~/.local/share/renv/ steps: - - name: "Checkout Lesson" uses: actions/checkout@v4 diff --git a/.github/workflows/update-cache.yaml b/.github/workflows/update-cache.yaml index a011c0c0..f314f29d 100644 --- a/.github/workflows/update-cache.yaml +++ b/.github/workflows/update-cache.yaml @@ -4,12 +4,12 @@ on: workflow_dispatch: inputs: name: - description: 'Who triggered this build (enter github username to tag yourself)?' + description: "Who triggered this build (enter github username to tag yourself)?" required: true - default: 'monthly run' + default: "monthly run" schedule: # Run every tuesday - - cron: '0 0 * * 2' + - cron: "0 0 * * 2" jobs: preflight: @@ -74,7 +74,6 @@ jobs: GITHUB_PAT: ${{ secrets.GITHUB_TOKEN }} RENV_PATHS_ROOT: ~/.local/share/renv/ steps: - - name: "Checkout Lesson" uses: actions/checkout@v4 diff --git a/.github/workflows/update-workflows.yaml b/.github/workflows/update-workflows.yaml index 6414cf28..9b53f82d 100644 --- a/.github/workflows/update-workflows.yaml +++ b/.github/workflows/update-workflows.yaml @@ -4,16 +4,16 @@ on: workflow_dispatch: inputs: name: - description: 'Who triggered this build (enter github username to tag yourself)?' + description: "Who triggered this build (enter github username to tag yourself)?" required: true - default: 'weekly run' + default: "weekly run" clean: description: 'Workflow files/file extensions to clean (no wildcards, enter "" for none)' required: false - default: '.yaml' + default: ".yaml" schedule: # Run every Tuesday - - cron: '0 0 * * 2' + - cron: "0 0 * * 2" jobs: check_token: