From e24147c3b80bacedce6eb8ffbc4ab58d9e56df2d Mon Sep 17 00:00:00 2001 From: jamesread Date: Wed, 9 Sep 2026 23:31:47 +0100 Subject: [PATCH] docs: clarify saveLogs writes per configured directory Each configured resultsDirectory or outputDirectory produces its own file; configuring only one directory writes only that file type. Co-authored-by: Cursor --- docs/modules/ROOT/pages/logs/saving.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/ROOT/pages/logs/saving.adoc b/docs/modules/ROOT/pages/logs/saving.adoc index 74243b5d..633bf1d3 100644 --- a/docs/modules/ROOT/pages/logs/saving.adoc +++ b/docs/modules/ROOT/pages/logs/saving.adoc @@ -3,7 +3,7 @@ By default, OliveTin only keeps logs in memory, meaning that if you restart OliveTin your logs will be lost. For some use cases this is acceptable, but you can configure OliveTin to save logs for you. -When `saveLogs` is enabled, OliveTin writes a results file and output file for every finished execution, including blocked runs (for example when concurrency or rate limits prevent the action from starting). +When `saveLogs` is enabled, OliveTin writes a file for each configured directory when an execution finishes — a results YAML when `resultsDirectory` is set, and an output log when `outputDirectory` is set. If only one directory is configured, only that file type is written. This includes blocked runs (for example when concurrency or rate limits prevent the action from starting). You can configure the global setting for saving logs, or override it on a per-action basis;