From a75a294cd1fac76e14c7890c364e6049a19e1203 Mon Sep 17 00:00:00 2001 From: stertooy <5571903+stertooy@users.noreply.github.com> Date: Fri, 31 Oct 2025 09:28:05 +0100 Subject: [PATCH 1/3] Fix reference nr 3 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 46e25bc..3574fb6 100644 --- a/README.md +++ b/README.md @@ -188,4 +188,4 @@ with this action or the FSF's own site. [1]: https://github.com/gap-system/ReleaseTools [2]: https://github.com/gap-actions/update-gh-pages -[2]: https://github.com/gap-actions/build-pkg-docs +[3]: https://github.com/gap-actions/build-pkg-docs From 2a7114a5f3fd3e2e039b0b546bd5b44168b167c0 Mon Sep 17 00:00:00 2001 From: stertooy <5571903+stertooy@users.noreply.github.com> Date: Fri, 31 Oct 2025 10:48:22 +0100 Subject: [PATCH 2/3] Update README.md --- README.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 3574fb6..86b908b 100644 --- a/README.md +++ b/README.md @@ -31,6 +31,13 @@ these steps: If everything is configured right, the new release of your package should appear on GitHub and your package's website within a few minutes. +> [!CAUTION] +> We strongly recommend a 'dry run' the first time you use this workflow. +> This will create an archive containing the release, which can be downloaded under +> the `Artifacts` in the relevant run of this workflow, but not actually publish the +> release. You can then inspect the release archive and, if satisfactory, re-run this +> workflow without the 'dry run' option. + ## Initial setup @@ -59,12 +66,12 @@ on: workflow_dispatch: inputs: dry-run: - description: "Only create an archive containing the release instead of publishing it on GitHub" + description: "Dry run: only create an archive containing the release instead of publishing it on GitHub" type: boolean required: false default: false force: - description: "Allow overwriting an existing release, or making a release with an incorrect date" + description: "Force: allow overwriting an existing release, or making a release with an incorrect date" type: boolean required: false default: false From 2af59982a21a9a41ee81c69acda6ba98fde44e1e Mon Sep 17 00:00:00 2001 From: stertooy <5571903+stertooy@users.noreply.github.com> Date: Tue, 4 Nov 2025 09:56:02 +0100 Subject: [PATCH 3/3] Update README.md Co-authored-by: Max Horn --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 86b908b..a9c9da3 100644 --- a/README.md +++ b/README.md @@ -32,7 +32,7 @@ If everything is configured right, the new release of your package should appear on GitHub and your package's website within a few minutes. > [!CAUTION] -> We strongly recommend a 'dry run' the first time you use this workflow. +> We recommend a 'dry run' the first time you use this workflow. > This will create an archive containing the release, which can be downloaded under > the `Artifacts` in the relevant run of this workflow, but not actually publish the > release. You can then inspect the release archive and, if satisfactory, re-run this