From b19612d3e35949dfd12bc3ace2642b43e5e33762 Mon Sep 17 00:00:00 2001 From: Timothy Date: Fri, 17 Jul 2026 18:50:22 +0200 Subject: [PATCH] probe: gitea if-skip status reporting (ersatztv#416, throwaway) --- .gitea/workflows/zz-skip-probe.yml | 31 ++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 .gitea/workflows/zz-skip-probe.yml diff --git a/.gitea/workflows/zz-skip-probe.yml b/.gitea/workflows/zz-skip-probe.yml new file mode 100644 index 000000000..4e159c54f --- /dev/null +++ b/.gitea/workflows/zz-skip-probe.yml @@ -0,0 +1,31 @@ +name: zz Skip Probe (ersatztv#416, throwaway) + +# THROWAWAY PROBE — do NOT merge. Answers ersatztv#416's central open question: +# on this Gitea/act_runner version, how is an `if:`-skipped job reported to the +# commit-status API that branch protection reads? success / pending / skipped / absent? +# Read `/commits//status` for this PR head after the run and delete the branch. + +on: + pull_request: + +jobs: + always-runs: + name: probe-always + runs-on: small + steps: + - run: echo "this job runs" + + skipped-literal: + name: probe-skipped-literal + runs-on: small + if: ${{ false }} + steps: + - run: echo "must NOT run" + + gated-on-needs: + name: probe-gated-on-needs + runs-on: small + needs: [always-runs] + if: ${{ needs.always-runs.result == 'success' && false }} + steps: + - run: echo "must NOT run (needs-gated)" -- 2.47.3