From 876b45fe5dfba820c38baadcafe665b9009f0ecd Mon Sep 17 00:00:00 2001
From: Dave Thomas <7sharp9@mail.com>
Date: Wed, 29 Jul 2026 15:46:18 +0100
Subject: [PATCH] fix(github): don't fail CI when publishing test results is
 blocked

Dependabot and fork PRs get a read-only GitHub token that can't post test-result annotations, which was failing otherwise good builds.

If we make that step non-blocking so a permissions issue with a reporting step doesn't mask a good build.
---
 .github/workflows/build.yml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index 0a3b665a..4cdc858a 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -48,7 +48,11 @@ jobs:
       run: dotnet fsi scripts/CheckSolutionVersions.fsx
 
     - name: Publish test results
+      # continue-on-error: Dependabot PRs (and PRs from forks) get a read-only GITHUB_TOKEN that GitHub forces 
+      # regardless of any `permissions:` blocks declared, so this step 403s on those runs. Test results are still
+      # in the build log so don't let that fail a good build due to this step.
       if: always() && runner.os == 'Linux'
+      continue-on-error: true
       uses: EnricoMi/publish-unit-test-result-action@d0a4676d0e0b938bc201470d88276b7c74c712b3 # v2.24.0
       with:
         files: '**/TestResults/**/*.trx'