GitHub Packages Docker Registry

GitHub Packages Docker Registry is the predecessor to GitHub Container Registry. If you're still pushing Docker images to GitHub Packages, it's recommended that you migrate to the newer GitHub Container Registry.

To give FeaturePeek the credentials to pull images from GitHub Packages, you need to ensure that one environment variable is present in your CI environment.

Note: This chapter is only applicable if you push images to GitHub Packages.

CI command

You'll need to pass in the -p flag when pinging FeaturePeek in your CI pipeline.

bash <(curl -s -p

Be sure to call this after your build step.

Required environment variables


If you are using a GitHub Actions workflow, the GITHUB_TOKEN secret gets generated for you on every CI run automatically. Simply point an environment variable of the same name to this secret in the Ping FeaturePeek step.

Below is an example workflow YAML file that builds a docker image and pushes it to the GitHub Packages registry. Be sure to replace ORG, REPO, IMAGE, and TAG with your own values.

The last line in the following example is how you set an environment variable to a secret.

# /.github/workflows/featurepeek.yml
name: Build and Ping FeaturePeek
on: push
runs-on: ubuntu-latest
node-version: [12.x]
- uses: actions/[email protected]
- name: Use Node.js ${{ matrix.node-version }}
uses: actions/setup-[email protected]
node-version: ${{ matrix.node-version }}
- name: Docker login
run: docker login -u ORG -p ${{ secrets.GITHUB_TOKEN }}
- name: Build and push image
run: |
docker build -t .
docker push
- name: Ping FeaturePeek
run: bash <(curl -s -p

You can also use a Personal Access Token instead of a secret — just replace ${{ secrets.GITHUB_TOKEN }} with your token value in both the Docker login and Ping FeaturePeek steps. Be sure to grant the token both read:packages and write:packages scopes when you create it.