From 7e1a84b40010b9763f5e3f1b7e1ca104b94ebe80 Mon Sep 17 00:00:00 2001 From: Earl Warren Date: Thu, 24 Jul 2025 05:22:06 +0000 Subject: [PATCH] fix: fails workflow validation if runs-on is missing (#192) This created confusion when the interpretation of the absence of `runs-on` changed unexpectedly. Making it mandatory fixes this ambiguity. Reviewed-on: https://code.forgejo.org/forgejo/act/pulls/192 Reviewed-by: Michael Kriese Co-authored-by: Earl Warren Co-committed-by: Earl Warren --- act/schema/workflow_schema.json | 1 + 1 file changed, 1 insertion(+) diff --git a/act/schema/workflow_schema.json b/act/schema/workflow_schema.json index b81af260..a976259c 100644 --- a/act/schema/workflow_schema.json +++ b/act/schema/workflow_schema.json @@ -1588,6 +1588,7 @@ }, "runs-on": { "description": "Use `runs-on` to define the type of machine to run the job on.\n* The destination machine can be either a GitHub-hosted runner, larger runner, or a self-hosted runner.\n* You can target runners based on the labels assigned to them, or their group membership, or a combination of these.\n* You can provide `runs-on` as a single string or as an array of strings.\n* If you specify an array of strings, your workflow will execute on any runner that matches all of the specified `runs-on` values.\n* If you would like to run your workflow on multiple machines, use `jobs..strategy`.", + "required": true, "context": ["forge", "github", "inputs", "vars", "needs", "strategy", "matrix"], "one-of": [ "non-empty-string",