Skip to content
This repository was archived by the owner on Sep 1, 2022. It is now read-only.

Commit c6cc949

Browse files
authored
Merge pull request #10 from githubtraining/Step1-typo-fix
Correct instructions to point to proper file
2 parents 7521041 + a6c9d92 commit c6cc949

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

responses/01_label-trigger.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ In a GitHub Actions workflow, the `on` step defines what causes the workflow to
2828
### :keyboard: Activity: Configure the workflow trigger based on an a label being added
2929

3030
1. Edit this file
31-
2. Change the name of the directory `CHANGETHIS` to `workflows`, so the title of this file with the path is `.github/workflows/staging-workflow.yml`
31+
2. Change the name of the directory `CHANGETHIS` to `workflows`, so the title of this file with the path is `.github/workflows/deploy-staging.yml`
3232
3. Edit the contents of this file to trigger on a label
3333

3434
Your result should look like this:

responses/03_workflow-steps.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ The course [_Using GitHub Actions for CI_](https://lab.github.com/githubtraining
2929
1. Click **Add a new secret** again.
3030
1. Name the second secret **AWS_SECRET_KEY** and paste the value from the Secret access key generated on AWS.
3131
1. Click **Add secret**
32-
1. Back in this pull request, edit the `.github/workflows/staging-workflow.yml` file to use a new action
32+
1. Back in this pull request, edit the `.github/workflows/deploy-staging.yml` file to use a new action
3333
```yml
3434
- name: Deploy to AWS
3535
uses: github/deploy-nodejs@master
@@ -82,4 +82,4 @@ jobs:
8282
env:
8383
AWS_ACCESS_KEY: {% raw %}${{ secrets.AWS_ACCESS_KEY }}{% endraw %}
8484
AWS_SECRET_KEY: {% raw %}${{ secrets.AWS_SECRET_KEY }}{% endraw %}
85-
```
85+
```

0 commit comments

Comments
 (0)