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

Commit f5e1c68

Browse files
committed
add quick-links for prod deployment workflow
1 parent a6ef550 commit f5e1c68

File tree

3 files changed

+10
-7
lines changed

3 files changed

+10
-7
lines changed

responses/09_merge-trigger.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,12 @@ Let's create a new workflow that deals specifically with commits to master and h
1010

1111
### :keyboard: Activity: Write the production deployment trigger on merge to master
1212

13-
1. Rename the file in this pull request to `.github/workflows/deploy-prod.yml`.
14-
1. Add a `push` trigger.
15-
1. Add `branches` inside the push block.
16-
1. Add `- master` inside the branches block.
17-
1. Commit your changes to this branch.
13+
1. Edit the `deploy-prod.yml` file on this branch, or [use this quick link]({{ repoUrl }}/edit/production-deployment-workflow/.github/CHANGETHIS/deploy-prod.yml?) _(We recommend opening the quick link in another tab)_
14+
2. Rename the file in this pull request to `.github/workflows/deploy-prod.yml`
15+
3. Add a `push` trigger
16+
4. Add `branches` inside the push block
17+
5. Add `- master` inside the branches block
18+
6. Commit your changes to this branch
1819

1920
The file should look like this when you're finished:
2021

responses/10_deploy-prod.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,10 @@ In our case, we can match our production environment to be exactly like our stag
1212

1313
### :keyboard: Commit the steps to the production workflow that allow you to deploy on merge to master
1414

15-
Add a `build` and `deploy` job to the workflow in this PR. It should look like the file below when you are finished.
15+
1. Edit the `deploy-prod.yml` file on this branch, or [use this quick link]({{ repoUrl }}/edit/production-deployment-workflow/.github/workflows/deploy-prod.yml?) _(We recommend opening the quick link in another tab)_
16+
2. Add a `build` and `deploy` job to the workflow
1617

17-
Note that not much has changed from our staging workflow, except for our trigger.
18+
It should look like the file below when you are finished. Note that not much has changed from our staging workflow, except for our trigger.
1819

1920
```yml
2021
name: Production deployment

responses/11_workflow-steps.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,7 @@ All of this happens automatically once a pull request is merged!
1111

1212
### :keyboard: Activity: Write the steps for the production deployment workflow
1313

14+
1. Edit the `deploy-prod.yml` file on this branch, or [use this quick link]({{ repoUrl }}/edit/production-deployment-workflow/.github/workflows/deploy-prod.yml?) _(We recommend opening the quick link in another tab)_
1415
1. Add a job to your workflow as follows:
1516
```yml
1617
Build-and-Push-Docker-Image:

0 commit comments

Comments
 (0)