Package registries allow developers to easily share code libraries and use them across different workstations. Some developers are already familiar with public package registries, such as npm or NuGet. Deploying private packages works in a similar way.

Development teams using GitHub Packages can share code libraries (such as npm, NuGet, Maven, or RubyGems) and containers directly within GitHub. These packages can be public or restricted to certain people, using the same secure GitHub identity for both code and packages. With GitHub Actions, you can automate the packaging and publishing of your code libraries and containers in just a few minutes.

In this module, you will learn how to use GitHub Actions to publish to GitHub Packages.

Learning Objectives

By the end of this module, you will be able to:

• Understand what a package registry is and when to use it
• Set up a Continuous Integration (CI) workflow with GitHub Actions to publish to GitHub Packages
• Validate your knowledge with an exercise testing your ability to publish to a GitHub Packages registry
• Identify how to authenticate, install, and manage GitHub packages

Prerequisites

• A GitHub account
• Basic knowledge of GitHub Actions