actions/cascading-pr
1
0
Fork 0
mirror of https://code.forgejo.org/actions/cascading-pr synced 2025-03-14 22:36:58 +01:00
Code Activity

README: explain where to find the logs in local debug mode

Browse source
This commit is contained in:
Earl Warren 2024-01-09 19:40:09 +01:00
parent 0ed38df165
commit ff13323a95
No known key found for this signature in database
GPG key ID: 0579CB2928A78A00
1 changed files with 9 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
README.md
View file

@ -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