From 2b01e2dc4f910e3e5c51de61ed2a22542d705849 Mon Sep 17 00:00:00 2001 From: Earl Warren Date: Sun, 20 Jul 2025 10:02:23 +0200 Subject: [PATCH] chore: test instructions with Forgejo v11.0.3 --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 5ca5928..1267e85 100644 --- a/README.md +++ b/README.md @@ -179,12 +179,13 @@ The test environment consists of the following (all users password is admin1234) git clone https://code.forgejo.org/actions/setup-forgejo export PATH=$(pwd)/setup-forgejo:$PATH git clone https://code.forgejo.org/actions/cascading-pr +export PATH=$(pwd)/cascading-pr:$PATH cd cascading-pr export DIR=/tmp/forgejo-for-cascading-pr forgejo-curl.sh logout forgejo-runner.sh teardown forgejo-binary.sh teardown -forgejo-binary.sh setup root admin1234 https://codeberg.org/forgejo/forgejo/releases/download/v1.21.3-0/forgejo-1.21.3-0-linux-amd64 +forgejo-binary.sh setup root admin1234 https://codeberg.org/forgejo/forgejo/releases/download/v11.0.3/forgejo-11.0.3-linux-amd64 FORGEJO_RUNNER_CONFIG=$(pwd)/tests/runner-config.yaml forgejo-runner.sh setup url=$(cat $DIR/forgejo-url) firefox $url @@ -207,7 +208,7 @@ The test for a successful run of the cascading-pr action consists of: Following the steps below recreate the same environment as the integration workflow locally. It is helpful for forensic analysis when -something does not run as expected and the error displayed are unclear. +something does not run as expected and the errors displayed are unclear. To help with the development loop all steps are idempotent and running `tests/run.sh --debug` multiple times must succeed.