summaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authorEarl Warren <contact@earl-warren.org>2023-11-04 14:20:32 +0100
committerEarl Warren <contact@earl-warren.org>2023-11-04 14:24:42 +0100
commit9a965f0d415fe5e8ef27886b83a8f364a43bc993 (patch)
tree528df423b9415fb018a841af188051f9b4342713 /README.md
parent[FORGEJO] cascade fork repo is cascading-pr/setup-forgejo (diff)
downloadforgejo-runner-9a965f0d415fe5e8ef27886b83a8f364a43bc993.tar.xz
forgejo-runner-9a965f0d415fe5e8ef27886b83a8f364a43bc993.zip
[FORGEJO] README updates
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index f62fe70..93cf659 100644
--- a/README.md
+++ b/README.md
@@ -10,7 +10,7 @@ The Forgejo runner depends on [a fork of ACT](https://code.forgejo.org/forgejo/a
Assuming the modifications to the [Forgejo runner](https://code.forgejo.org/forgejo/runner) are pushed to a fork in a branch named `wip-runner-change`, a pull request will verify it compiles and the binary is sane (running `forgejo-runner --version`). It will not verify that it is able to properly run jobs when connected to a live Forgejo instance.
-For end to end testing, a [workflow](https://code.forgejo.org/forgejo/runner/src/branch/main/.forgejo/workflows/cascade-setup-forgejo.yml) will create a [cascading-pr](https://code.forgejo.org/actions/cascading-pr/) in [setup-forgejo](https://code.forgejo.org/actions/setup-forgejo/pulls) and wait for its success.
+For end to end testing, a [workflow](https://code.forgejo.org/forgejo/runner/src/branch/main/.forgejo/workflows/cascade-setup-forgejo.yml) will [create a PR](https://code.forgejo.org/actions/cascading-pr/) in [setup-forgejo](https://code.forgejo.org/actions/setup-forgejo/pulls) and wait for its success.
The runner can be released by merging the `wip-runner-change` branch and by pushing a new tag, for instance `v10.2.3`. For more information see the [documentation that details this release process](https://forgejo.org/docs/next/developer/RELEASE/#forgejo-runner-publication) in the Forgejo infrastructure. Once published, the [setup-forgejo](https://code.forgejo.org/actions/setup-forgejo/) action can be updated to default to this latest version knowing it already passed integration tests.