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

Commit a1888c3

Browse files
authored
Merge pull request #16 from githubtraining/add-packages
Add GitHub Packages
2 parents e9f20ef + 7b15d7a commit a1888c3

File tree

3 files changed

+8
-6
lines changed

3 files changed

+8
-6
lines changed

config.yml

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -272,16 +272,18 @@ steps:
272272
# We validate
273273
# - type: gate
274274

275-
# Step 11: Create the Docker image and push it to GPR
275+
276+
# Step 11: Create the Docker image and push it to GitHub Packages
277+
276278

277279
# We tell the user to write the proper steps for the workflow
278280
- type: respond
279281
with: 11_workflow-steps.md
280282

281283
# event: commit, user writes the steps for the workflow, using recommended existing GitHub steps
282284

283-
- title: Create the Docker image and push it to GPR
284-
description: Add a step to the workflow for building and pushing a Docker image to GPR.
285+
- title: Create the Docker image and push it to GitHub Packages
286+
description: Add a step to the workflow for building and pushing a Docker image to GitHub Packages.
285287
event: pull_request
286288
link: '{{ repoUrl }}/pull/3'
287289
actions:

responses/11_workflow-steps.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
# Workflow steps
22

3-
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.
3+
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.
44

5-
We'll only use one new action here created by a GitHubber, which allows us to push a container to GPR.
5+
We'll only use one new action here created by a GitHubber, which allows us to push a container to GitHub Packages.
66
- `mattdavis0351/actions/docker-gpr`
77

88
All of this happens automatically once a pull request is merged!

responses/12_congratulations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
## Nice work!
22

3-
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.
3+
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.
44

55
![celebrate](https://octodex.github.com/images/jetpacktocat.png)
66

0 commit comments

Comments
 (0)