diff --git a/config.yml b/config.yml index f165612..fd8a973 100644 --- a/config.yml +++ b/config.yml @@ -272,7 +272,9 @@ steps: # We validate # - type: gate -# Step 11: Create the Docker image and push it to GPR + +# Step 11: Create the Docker image and push it to GitHub Packages + # We tell the user to write the proper steps for the workflow - type: respond @@ -280,8 +282,8 @@ steps: # event: commit, user writes the steps for the workflow, using recommended existing GitHub steps -- 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. +- title: Create the Docker image and push it to GitHub Packages + description: Add a step to the workflow for building and pushing a Docker image to GitHub Packages. event: pull_request link: '{{ repoUrl }}/pull/3' actions: diff --git a/responses/11_workflow-steps.md b/responses/11_workflow-steps.md index 5221f3e..8347640 100644 --- a/responses/11_workflow-steps.md +++ b/responses/11_workflow-steps.md @@ -1,8 +1,8 @@ # Workflow steps -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. +We'll add a final section to our production workflow that packages up our application in a Docker container and publishes it to GitHub Packages. This step is important for the traceability of your deployed artifacts. -We'll only use one new action here created by a GitHubber, which allows us to push a container to GPR. +We'll only use one new action here created by a GitHubber, which allows us to push a container to GitHub Packages. - `mattdavis0351/actions/docker-gpr` All of this happens automatically once a pull request is merged! diff --git a/responses/12_congratulations.md b/responses/12_congratulations.md index 7ff44be..8c22948 100644 --- a/responses/12_congratulations.md +++ b/responses/12_congratulations.md @@ -1,6 +1,6 @@ ## 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. +Now, we just have to wait for the deployment to occur, and for the package to be published to GitHub Packages. 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)