Testing CI

.github/workflows/ci-build.yml

@@ -78,8 +78,10 @@ jobs:
       # receives its workflow status.
       #
       # Workaround this by setting a status check to the new head manually.
+      #
+      # This does not work for forked repositories.
       - name: Set status check
-        if: always()
+        if: always() && !github.event.pull_request.head.repo.fork
         env:
           GH_TOKEN: ${{ github.token }}      
         run: |

README.md

@@ -29,7 +29,7 @@ didn't mess up your content. This usually only happens when using the
 [admonition syntax](https://docusaurus.io/docs/markdown-features/admonitions#usage-with-prettier).
 
 If you're submitting a PR from a fork, or otherwise want to format your code
-locally, use:
+locally, use asdfasdf:
 
 ```bash
 npx prettier --write .

docs/command-line-tutorial.md

@@ -212,10 +212,9 @@ Saved new collector credential to /your/current/directory/collector-credential-1
 
 :::warning
 
-This credential isn't sensitive because it's only useful in your local
-instance of Divvi Up. But collector credentials generated against the production
-service should be carefully managed. Consider using a password manager to
-protect them.
+This credential isn't sensitive because it's only useful in your local instance
+of Divvi Up. But collector credentials generated against the production service
+should be carefully managed. Consider using a password manager to protect them.
 
 :::