@@ -147,6 +147,11 @@ pull request. GitHub has safeguarded the token used in this workflow to have no
147147priviledges in the repository, but we have taken precautions to protect against
148148spoofing.
149149
150+ This workflow is triggered with every push to a pull request. If this workflow
151+ is already running and a new push is sent to the pull request, the workflow
152+ running from the previous push will be cancelled and a new workflow run will be
153+ started.
154+
150155The first step of this workflow is to check if it is valid (e.g. that no
151156workflow files have been modified). If there are workflow files that have been
152157modified, a comment is made that indicates that the workflow is not run. If
@@ -160,7 +165,7 @@ request. This builds the content and uploads three artifacts:
1601653 . The rendered files (build)
161166
162167Because this workflow builds generated content, it follows the same general
163- process as the sandpaper-main workflow with the same caching mechanisms.
168+ process as the ` sandpaper-main ` workflow with the same caching mechanisms.
164169
165170The artifacts produced are used by the next workflow.
166171
@@ -176,7 +181,7 @@ The steps in this workflow are:
1761813 . If it is valid: update the pull request comment with the summary of changes
177182
178183Importantly: if the pull request is invalid, the branch is not created so any
179- malicious code is not published.
184+ malicious code is not published.
180185
181186From here, the maintainer can request changes from the author and eventually
182187either merge or reject the PR. When this happens, if the PR was valid, the
0 commit comments