STACKITGit/end-to-end
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

test: test cloning of private reusable workflows (#1436)

Browse source 
Verify that Forgejo Runner can access a reusable workflow that is stored in a private repository.

That should help prevent https://code.forgejo.org/forgejo/runner/issues/1274 from happening again.

Reviewed-on: https://code.forgejo.org/forgejo/end-to-end/pulls/1436
Reviewed-by: Mathieu Fenniak <mfenniak@noreply.code.forgejo.org>
Co-authored-by: Andreas Ahlenstorf <andreas@ahlenstorf.ch>
Co-committed-by: Andreas Ahlenstorf <andreas@ahlenstorf.ch>
This commit is contained in:
Andreas Ahlenstorf 2026-01-18 20:15:11 +00:00 • committed by Mathieu Fenniak
parent 03ee700046
commit 25c472b90b
5 changed files with 65 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

10
actions/example-private-workflow-call/.forgejo/workflows/reusable.yaml Normal file
View file

@ -0,0 +1,10 @@
on:
workflow_call:
jobs:
build:
runs-on: "docker"
container:
image: data.forgejo.org/oci/node:24-trixie
steps:
- run: echo 'OK'

11
actions/example-private-workflow-call/.forgejo/workflows/test.yaml Normal file
View file

@ -0,0 +1,11 @@
on:
push:
jobs:
test:
# `runs-on` disables workflow expansion. We want that in this case, because then Forgejo Runner has to authenticate
# itself to access the reusable workflow.
runs-on: docker
container:
image: data.forgejo.org/oci/node:24-trixie
uses: ./.forgejo/workflows/reusable.yaml