From 2c2e2d58889744ba7209f975aa1671f769981ffa Mon Sep 17 00:00:00 2001 From: Graham Savage Date: Fri, 26 Jun 2026 13:34:16 +0100 Subject: [PATCH] Use ref input as KOSLI_TRAIL when provided Allow the ref input to drive the KOSLI_TRAIL value, falling back to the previous logic (PR head SHA, then github.sha) when ref is empty. This supports CyberDojo's co-promotion workflow, where one GitHub repository uses these workflows to deploy changes originating from a different CyberDojo repository. In that case the Kosli trail must be keyed on the supplied ref rather than the calling repository's own SHA. Co-Authored-By: Claude Opus 4.8 (1M context) --- .github/workflows/base.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/base.yml b/.github/workflows/base.yml index f6e72c0..79a08c6 100644 --- a/.github/workflows/base.yml +++ b/.github/workflows/base.yml @@ -71,7 +71,7 @@ jobs: KOSLI_HOST: ${{ inputs.kosli_host }} KOSLI_API_TOKEN: ${{ secrets.kosli_api_token }} KOSLI_FLOW: ${{ inputs.kosli_flow }} - KOSLI_TRAIL: ${{ github.event.pull_request.head.sha || github.sha }} + KOSLI_TRAIL: ${{ inputs.ref || github.event.pull_request.head.sha || github.sha }} permissions: id-token: write contents: write