enhance(report): add runner.log_report_level for the uploaded runner messages (#1310)

The runner's own messages between steps (not step output) were uploaded to the job log at `log.level`, so raising `log.level` for local debugging also changed what workflow authors see in Gitea, and lowering it hid messages from them. Add `runner.log_report_level` to set that independently. Unset, it still follows `log.level`, so existing setups behave as before. An invalid value is rejected when the config loads. Assisted-by: Codet Assisted-by: Claude Code:claude-opus-5-5 Co-authored-by: silverwind <[email protected]> Co-authored-by: silverwind <[email protected]> Reviewed-on: https://gitea.com/gitea/runner/pulls/1310 Co-authored-by: Lunny Xiao <[email protected]>
2026-11-09 00:30:28 +00:00 · 2026-10-14 14:15:26 +00:00
1 parent 42858c61df
commit 9c4c66e70f
@@ -40,6 +40,9 @@ fields.

 - The process-wide logger masks the secrets of every live task, the job logger masks its own.
  Going around either leaks them.
+- The job logger's output can reach the job log workflow authors see, the process-wide logger's
+  stays on the runner host, so keep operator-only detail (host paths, internal addresses) off the
+  job logger.
 - Libraries that log through logrus's or slog's global logger are forwarded to the process-wide
  one, so they follow its level and masking too.
 - That forwarding only works while logrus's global logger is left as `logging` configures it. A