alexandClaude Opus 5
a9469448fc
Probe the artifacts / probe (push) Successful in 8s
The first round answered what it was for: a step cannot set GITHUB_SERVER_URL and v4 fails on the check either way, while v3 uploads. The three upload steps are down to one, on the fork, and it is no longer allowed to fail quietly — the run is now a straight yes or no on going back to v4. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
50 lines
1.5 KiB
YAML
50 lines
1.5 KiB
YAML
# 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
|