From e91adade9a04a95754bd2f9e8a21872c9df93d6d Mon Sep 17 00:00:00 2001 From: Gitea Bot Date: Tue, 17 Nov 2026 08:38:34 +0000 Subject: [PATCH] Update the runner reference pages (#651) Automated update of the generated runner reference pages from gitea/runner (main for the develop docs, the newest stable tag for every documented series), opened by the "update runner reference" scheduled workflow. Preview: https://pr-651.docs-gitea-com.pages.dev Reviewed-on: https://gitea.com/gitea/docs/pulls/651 Reviewed-by: silverwind <2021+silverwind@noreply.gitea.com> Co-authored-by: Gitea Bot --- runner-docs/reference/config-example.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/runner-docs/reference/config-example.md b/runner-docs/reference/config-example.md index 950244b4..74627c2a 100644 --- a/runner-docs/reference/config-example.md +++ b/runner-docs/reference/config-example.md @@ -58,7 +58,7 @@ runner: #client_cert_file: /etc/gitea-runner/client.crt #client_key_file: /etc/gitea-runner/client.key # PEM CA certificates of a Gitea instance with a private CA, trusted besides the system's. - # Runner-side git and builtin:checkout use it instead of the system's bundle for the instance. + # Runner-side git uses it instead of the system's bundle for the instance. # Jobs get it at /var/run/act/ca.crt, or in their act directory on the host, with NODE_EXTRA_CA_CERTS # pointing there unless the job, or on Docker its image, sets it. Other tools in jobs, such as the # git that actions/checkout runs, need the CA in the image's bundle, for example via container.volumes. @@ -145,8 +145,8 @@ runner: # What to mount at RUNNER_TOOL_CACHE (/opt/hostedtoolcache), where setup actions install tools: # none: nothing. A docker job sees what its image ships there, a host job an empty dir, and # either way what it installs is gone when the job ends. - # shared: one tool cache every job reuses. Two jobs writing the same tool version at once - # corrupt it, so use it only with capacity 1. + # shared: one tool cache per capacity slot, reused by later jobs. It hides the tools later job + # images ship, so use images without them. #tool_cache_mode: none # Optional executable on the host, run once after each task's built-in cleanup # (post-steps, container teardown, bind-workdir removal). Additive only.