From 1e25fc9c4685aa16f484e532d2377754ab8daf2e Mon Sep 17 00:00:00 2001 From: Aniruddha Adak Date: Tue, 29 Sep 2026 14:48:43 +0530 Subject: [PATCH] Clarify that working-directory only applies to run steps The jobs..steps[*].working-directory section documented the keyword without stating that it is only valid on steps that use un. The workflow schema marks a step that sets working-directory without un as invalid, so the page left readers to assume a constraint that the product actually enforces. Fixes #42699 --- .../actions/reference/workflows-and-actions/workflow-syntax.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/actions/reference/workflows-and-actions/workflow-syntax.md b/content/actions/reference/workflows-and-actions/workflow-syntax.md index 5f916e52265e..94b27067d1a2 100644 --- a/content/actions/reference/workflows-and-actions/workflow-syntax.md +++ b/content/actions/reference/workflows-and-actions/workflow-syntax.md @@ -868,7 +868,7 @@ Each `run` keyword represents a new process and shell in the runner environment. ## `jobs..steps[*].working-directory` -Using the `working-directory` keyword, you can specify the working directory of where to run the command. +Using the `working-directory` keyword, you can specify the working directory of where to run the command. You can only use `working-directory` in a step that runs a command with `run`. You cannot use it in a step that calls an action with `uses`. ```yaml - name: Clean temp directory