From a1ead9463aaada2a3d88dfe63c618d6309b24dfa Mon Sep 17 00:00:00 2001 From: Earl Warren Date: Mon, 4 Dec 2023 18:37:56 +0100 Subject: [PATCH] developer: release: fix typo --- docs/developer/RELEASE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/developer/RELEASE.md b/docs/developer/RELEASE.md index 04db9b00..94189c70 100644 --- a/docs/developer/RELEASE.md +++ b/docs/developer/RELEASE.md @@ -112,7 +112,7 @@ VPN and its role is to copy and sign release artifacts. - Binaries are downloaded from https://code.forgejo.org/forgejo-integration/runner, signed and copied to https://code.forgejo.org/forgejo/runner. - Container images are copied from https://code.forgejo.org/forgejo-integration to https://code.forgejo.org/forgejo -If the publishing the release needs debug, it can be done manually: +If publishing the release needs debug, it can be done manually: - https://forgejo.octopuce.forgejo.org/forgejo-release/runner-debug has the same secrets as https://forgejo.octopuce.forgejo.org/forgejo-release/runner - Make the changes, commit them, tag the commit with vX.Y.Z-N and force push the tag to https://forgejo.octopuce.forgejo.org/forgejo-release/runner-debug. Note that it does not matter that the tag is not on a commit that matches the release because this action only cares about the tag: it does not build any content itself, it copies it from one organization to another. However it matters that it matches a SHA that is found in the destination repository of the release otherwise it won't be able to set the tag (setting a tag on a non-existing sha does not work).