wrap it up

Author: hectorsector

config.yml

@@ -267,16 +267,16 @@ steps:
   # We validate
   # - type: gate
 
-# Step 11: Write the steps for the production workflow
+# Step 11: Create the Docker image and push it to GPR
 
   # We tell the user to write the proper steps for the workflow
   - type: respond
     with: 11_workflow-steps.md
 
   # event: commit, user writes the steps for the workflow, using recommended existing GitHub steps
 
-- title: Write the steps for the production workflow
-  description: Write the steps for the production deployment to the workflow file
+- title: Create the Docker image and push it to GPR
+  description: Add a step to the workflow for building and pushing a Docker image to GPR.
   event: pull_request
   link: '{{ repoUrl }}/pull/3'
   actions:
@@ -306,12 +306,7 @@ steps:
 
   # check that its merged
   - type: gate
-    every: true
-    gates:
-    - left: '%payload.action%'
-      operator: ===
-      right: closed
-    - left: '%payload.pull_request.merged%'
+    left: '%payload.pull_request.merged%'
 
 # final response: congratulations
   - type: respond

responses/11_workflow-steps.md

@@ -1,24 +1,42 @@
 # Workflow steps
 
-So far, the workflow knows what the trigger is and what environment to run in. But, what exactly is supposed to run? The "steps" section of this workflow specify what actions to be run in the Ubuntu environment when new labels are added.
+We'll add a final section to our production workflow that packages up our application in a Docker container and publishes it to the GitHub Package Registry (GPR). This step is important for the traceability of your deployed artifacts.
 
-With the staging deployment, we use `checkout` and `Deploy to AWS`. In this workflow, we use: 
-
-- `actions/checkout@v1`
-- `Deploy to AWS`
-
-We also have a new section past the `deploy` section, called **Docker Build, Tag, Push**, or Build-and-Push-Docker-Image. This part of the workflow uses the action from another course. That action builds the code, tags the commit, and pushes a package to the GitHub Package Registry.
-
-- `actions/checkout@v1`
-- `actions/download-artifact@master`
-- `mattdavis0351/actions/docker-gpr@v1`
+We'll only use one new action here created by a GitHubber, which allows us to push a container to GPR. 
+- `mattdavis0351/actions/docker-gpr`
 
 All of this happens automatically once a pull request is merged!
 
 ## Step 11: Write the steps for the production workflow
 
 ### :keyboard: Activity: Write the steps for the production deployment workflow
 
+1. Add a job to your workflow as follows:
+    ```yml
+    Build-and-Push-Docker-Image:
+    runs-on: ubuntu-latest
+    needs: build
+    name: Docker Build, Tag, Push
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v1
+
+      - name: Download built artifact
+        uses: actions/download-artifact@master
+        with:
+          name: webpack artifacts
+          path: public
+
+      - name: Build, Tag, Push
+        uses: mattdavis0351/actions/docker-gpr@v1
+        with:
+          repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+          image-name: tic-tac-toe
+    ```
+1. Commit the workflow to this branch.
+
+The complete workflow file should look like this:
+
 ```yml
 name: Production deployment
 

responses/12_congratulations.md

@@ -1,7 +1,9 @@
 ## Nice work!
 
+Now, we just have to wait for the deployment to occur, and for the package to be published to GPR. When it's completed, you should be able to see it in the [Packages]({{ repoUrl }}/packages) section of your repository. You can get the deployment URL in the [Actions]({{ repoUrl }}/actions) log, just like the staging URL.
+
 ![celebrate](https://octodex.github.com/images/jetpacktocat.png)
 
-You merged and this course is now complete! I'll stop responding but the fun doesn't have to stop here. 
+This course is now complete! I'll stop responding but the fun doesn't have to stop here. 
 
 Now...[what will you learn next]({{ host }}/courses)?