Skip to content

Commit c86b80b

Browse files
authored
Merge pull request #43662 from github/repo-sync
Repo sync
2 parents 2deb076 + fdf0404 commit c86b80b

File tree

2 files changed

+3
-1
lines changed

2 files changed

+3
-1
lines changed

content/actions/using-workflows/workflow-syntax-for-github-actions.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -615,6 +615,8 @@ Each `run` keyword represents a new process and shell in the runner environment.
615615
npm run build
616616
```
617617

618+
## `jobs.<job_id>.steps[*].working-directory`
619+
618620
Using the `working-directory` keyword, you can specify the working directory of where to run the command.
619621

620622
```yaml

data/reusables/actions/workflow-basic-example-and-explanation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ on: [push]
5757
# Groups together all the steps that run in the `check-bats-version` job. Each item nested under this section is a separate action or shell script.
5858
steps:
5959

60-
# The `uses` keyword specifies that this step will run `v3` of the `actions/checkout` action. This is an action that checks out your repository onto the runner, allowing you to run scripts or other actions against your code (such as build and test tools). You should use the checkout action any time your workflow will use the repository's code.
60+
# The `uses` keyword specifies that this step will run `v4` of the `actions/checkout` action. This is an action that checks out your repository onto the runner, allowing you to run scripts or other actions against your code (such as build and test tools). You should use the checkout action any time your workflow will use the repository's code.
6161
- uses: {% data reusables.actions.action-checkout %}
6262

6363
# This step uses the `{% data reusables.actions.action-setup-node %}` action to install the specified version of the Node.js. (This example uses version 14.) This puts both the `node` and `npm` commands in your `PATH`.

0 commit comments

Comments
 (0)