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

actions: use the forgejo context instead of forge and test backward compatibility (#1034)

Browse source 
Reviewed-on: https://code.forgejo.org/forgejo/end-to-end/pulls/1034
Reviewed-by: Mathieu Fenniak <mfenniak@noreply.code.forgejo.org>
Reviewed-by: Michael Kriese <michael.kriese@gmx.de>
Co-authored-by: Earl Warren <contact@earl-warren.org>
Co-committed-by: Earl Warren <contact@earl-warren.org>
This commit is contained in:
Earl Warren 2025-12-01 13:59:46 +00:00 • committed by Michael Kriese
parent 7f6f69c80f
commit 14d2748a33
No known key found for this signature in database
GPG key ID: F128CBE6AB3A7201
5 changed files with 28 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

4
actions/example-docker-action/.forgejo/workflows/test.yml
View file

@ -9,11 +9,11 @@ jobs:
#
- uses: https://code.forgejo.org/forgejo/test-setup-forgejo-docker@main
with:
args: ${{ forge.workspace }}/SOMEFILE
args: ${{ forgejo.workspace }}/SOMEFILE
#
# ... which then also exists in the job workspace
# because both docker containers are automatically
# sharing the volume that contains it.
#
- run: |
test -f ${{ forge.workspace }}/SOMEFILE
test -f ${{ forgejo.workspace }}/SOMEFILE