# A throwaway workflow: it answers, in seconds, what the release cannot ask
# without building for four minutes first.
#
# The first round of it settled the question it was written for. The runner sets
# the GITHUB_ names over the env of a step, so GITHUB_SERVER_URL cannot be
# corrected from a workflow and the host check inside upload-artifact v4 cannot
# be talked out of its verdict; v3 uploaded and v4 did not, either way.
#
# What is left to see is whether the fork works — the same v4 action taken from
# this Gitea with that one check removed. Nothing here is allowed to fail
# quietly: a green run means the release can go back to v4.
#
# Delete this file once the release works
name: Probe the artifacts

on:
  workflow_dispatch:
  push:
    branches:
      - 'probe/**'

defaults:
  run:
    shell: pwsh

jobs:
  probe:
    runs-on: windows-x64

    steps:
      - name: Make a file to upload
        run: |
          New-Item -ItemType Directory -Force probe | Out-Null
          'probe' | Out-File probe/probe.txt -Encoding utf8

      # Kept for the record: ACTIONS_RESULTS_URL is the v4 backend the check
      # never let the action reach
      - name: Show the environment
        run: |
          "server = [$env:GITHUB_SERVER_URL]"
          "api    = [$env:GITHUB_API_URL]"
          "results= [$env:ACTIONS_RESULTS_URL]"

      - name: Upload with the fork
        uses: https://git.alrakis.kz/actions/upload-artifact@v4-gitea
        with:
          name: probe-fork
          path: probe/
          if-no-files-found: error