From ff13323a950cdd8310c5c1db2388e744ad1496d0 Mon Sep 17 00:00:00 2001 From: Earl Warren Date: Tue, 9 Jan 2024 19:40:09 +0100 Subject: [PATCH] README: explain where to find the logs in local debug mode --- README.md | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index eef5c1e..0dce097 100644 --- a/README.md +++ b/README.md @@ -220,18 +220,21 @@ For instance: * `./cascading-pr.sh --debug --origin-url ... upsert_branch` will only call the `upsert_branch` function found in `cascading-pr.sh`. -## directories - -The `tests/run.sh` script stores all its files in -`/tmp/cascading-pr-test`. The temporary directories created by -`cascading-pr.sh` are disposed of when the script ends. - ## logging If `--debug` is used a full debug log is displayed, very complete and very verbose. Otherwise it is stashed in a temporary file and only displayed if an error happens. +If all goes well, the runner logs are not displayed even with `--debug`. They +can be looked at in the web UI. + +## directories + +The `tests/run.sh` script stores all its files in +`/tmp/cascading-pr-test`. The temporary directories created by +`cascading-pr.sh` are disposed of when the script ends. + ## snippets for copy/pasting ```sh