feat: add Screeps console monitoring with configurable error handling and shard support (#84)

Reviewed-on: #84
2026-05-16 19:44:39 +02:00
parent be3c8ac7d2
commit bf52580bf3
12 changed files with 3124 additions and 18 deletions
@@ -26,6 +26,19 @@ To use this action, you need to set it up in your workflow .yml file located in
 - `pattern`: Glob pattern to match files (default: *.js).
 - `branch`: Branch in Screeps to which the code will be uploaded (default: default).
 - `git-replace`: Overwrite "{{gitRef}}", "{{gitHash}}" and "{{deployTime}}" values in files matching the pattern.
+- `shard`: The Screeps shard to monitor (e.g. `shard0`, `shard1`). Defaults to `shard0` on the official server.
+- `monitor`: Number of game ticks to monitor the Screeps console after deploying (0 = disabled, default: 0).
+- `log_to_file`: If `true`, buffers stdout to an artifact file instead of streaming live (default: false). Note: Errors and warnings always stream live.
+- `on_traceback`: Action on JS traceback detection: `ignore`, `warn`, or `fail` (default: `fail`).
+- `on_error_log`: Action on Screeps error-console output: `ignore`, `warn`, or `fail` (default: `warn`).
+- `on_warning_log`: Action on `console.warn` output: `ignore`, `warn`, or `fail` (default: `ignore`).
+- `monitor_interval`: Print a progress update every N ticks (default: 10).
+
+## Outputs
+
+- `saw_traceback`: `true` if a JS traceback was detected during monitoring.
+- `saw_error_log`: `true` if the Screeps error console had output during monitoring.
+- `saw_warning_log`: `true` if `console.warn` output was detected during monitoring.

 Example Workflow