adding final responses

Author: mattdavis0351

config.yml

@@ -377,4 +377,13 @@ steps:
     actions:
       - type: createIssue
         title: Last minute notes
-        body: 16_using-ncc.md
+        body: great-job.md
+      - type: respond
+        issue: Last minute notes
+        with: 16_using-ncc.md
+      - type: respond
+        issue: Last minute notes
+        with: 16_publishing.md
+      - type: respond
+        issue: Last minute notes
+        with: 16_complete.md

responses/16_complete.md

@@ -0,0 +1,15 @@
+## The End 😭
+
+It was so fun having you as a student while taking this course. I'll forever cherish our time together {{user.login}}
+
+You can keep this repository forever to remember our time... I actually encourage you to do so! This has now become your central point for notes on writing JavaScript Actions 😄
+
+I really do think of everything!
+
+Make sure to visit [Learning Lab](lab.github.com) for more courses on GitHub Actions and other awesome tech content.
+
+We would love to hear what you thought about this course, share your experience with us and others in the [Community forum](https://github.community/t5/GitHub-Learning-Lab/bd-p/learn)
+
+---
+
+To fully complete your course **close this issue**

responses/16_publishing.md

@@ -0,0 +1,14 @@
+## Publishing your Actions
+
+Publishing your Actions is a great way to help others in your team and across the GitHub community. Although Actions do not need to be published to be consumed by adding them to the marketplace you make them easier to find.
+
+Some notable Actions you will find on the marketplace are:
+
+- [Actions for Discord](https://github.com/marketplace/actions/actions-for-discord)
+- [GitHub Action for Slack](https://github.com/marketplace/actions/github-action-for-slack)
+- [Jekyll Action](https://github.com/marketplace/actions/jekyll-action)
+- [Run Jest](https://github.com/marketplace/actions/run-jest)
+
+And that just scratches the surface of the 1600+ and counting Actions you will find on the marketplace 😄
+
+📖Follow [this guide](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/publishing-actions-in-github-marketplace#publishing-an-action) to learn how to publish your Actions to the GitHub Marketplace

responses/16_using-ncc.md

@@ -0,0 +1,39 @@
+## Getting rid of node_modules
+
+We typically don't commit a `node_modules` folder in a repository. These can often grow to be huge if your project has many dependencies. Because of the way Node works this folder is a necessary evil, but there is a way to get rid of it!
+
+First you need to install a tool called [ncc](https://github.com/zeit/ncc). You'll want to install this tool globally so that you can use as if it's any other CLI tool on your machine.
+
+What **ncc** does is take all the dependencies within your project and compile them into a single JavaScript file. This allows you to avoid committing the `node_modules` folder in your Actions source code.
+
+**Install ncc**
+`npm install -g @zeit/ncc`
+
+**Using ncc**
+When you use ncc:
+
+`ncc build <input-file>`
+
+A new directory named `dist` will be created. Within that directory you will find a file named `index.js`. To tell GitHub Actions that this new `index.js` file is the one that should run when your Action is used a small edit to the `action.yml` file needs to be made.
+
+_before:_
+
+```yaml
+runs:
+  using: "node12"
+  main: "index.js"
+```
+
+_after:_
+
+```yaml
+runs:
+  using: "node12"
+  main: "dist/index.js"
+```
+
+Once you make this change you can delete the `node_modules` folder and commit those changes to the repository that contains your Actions source code.
+
+---
+
+📖Further help [using ncc](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/creating-a-javascript-action#commit-and-push-your-action-to-github) is in the GitHub Actions documentation.

responses/great-job.md

@@ -0,0 +1,44 @@
+# Great job!
+
+You did it 🎉
+
+You have successfully written three different JavaScript Actions.
+
+Let's take a quick look at all the things you learned in this course:
+
+**Workflows**
+Along the way you learned a little about workflows and how to configure them. You managed to accomplish all these things:
+
+- Define two different event triggers
+- Filter an event trigger to run only when a label is added to a pull request
+- You configured one unique job containing three unique steps within a workflow
+- You learned how to overwrite default Action values by defining them in a workflow
+- One of your steps consumed a secret
+- One of your steps consumed the output of a previous step
+
+That's quite a bit for a course that doesn't cover workflows!
+
+**Action metadata**
+
+- You became familiar with over 1/2 of the syntax keywords that can be used in an `action.yml` file
+- Using `inputs:` and `outputs:` allowed you to create more dynamic and reusable metadata files for your Actions.
+- You've mow written the metadata for three different Actions
+
+**JavaScript Actions**
+Wow, what a series of tasks! You started with the traditional `hello world` in the console, which was then expanded to use the `input:` parameters specified in the Actions metadata. Through the use of that metadata you were able to be flexible with your greeting.
+
+You learned how GitHub Actions behave when consuming external APIs and you also used the response from an external API as an `output:` parameter for a later step in the workflow.
+
+Lastly you saw how to use Actions to interact with a repository by creating an issue containing a joke.
+
+You used multiple packages in your Action source code, you consumed `inputs:` and set `outputs:`.
+
+You learned how to use the `@actions/core` package to write errors and terminate a misbehaving Action.
+
+At this point you are armed with everything you need to know to go out there and begin creating your own custom JavaScript Actions.
+
+### We aren't done yet 😉
+
+Throughout this course I have promised to show you how to get rid of the `node_modules` folder in your repository.
+
+I also want to take a few minutes to point you to the information you need to place your own custom Actions on the [GitHub Marketplace](https://github.com/marketplace?type=actions) for others to use.