CI: Gitea-Upload-Schritt loggt Token-Laenge zur Diagnose

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-08-21 00:37:54 +02:00
parent 18e6a597cc
commit 9a61cad54b
1 changed files with 3 additions and 1 deletions
@@ -119,8 +119,10 @@ jobs:
          MSI_NAME:    ${{ steps.build.outputs.MSI_NAME }}
          COMMIT_SHA:  ${{ github.sha }}
        run: |
+          $tokLen = if ([string]::IsNullOrEmpty($env:GITEA_TOKEN)) { 0 } else { $env:GITEA_TOKEN.Length }
+          Write-Host "Diagnose: GITEA_TOKEN Laenge = $tokLen (0 = Secret erreicht den Lauf nicht)"
          if ([string]::IsNullOrWhiteSpace($env:GITEA_TOKEN)) {
-            Write-Host "::notice::GITEA_TOKEN nicht gesetzt — Gitea-Upload uebersprungen."
+            Write-Host "::warning::GITEA_TOKEN leer (Laenge=$tokLen) — Gitea-Upload uebersprungen. Muss ein REPOSITORY-Secret sein unter Settings > Secrets and variables > Actions (Tab 'Secrets', NICHT 'Variables'), Name exakt GITEA_TOKEN, im Repo mwende/Intune-Manager."
            exit 0
          }
          $headers = @{ Authorization = "token $env:GITEA_TOKEN" }