Fork Repository

Update GitHub Actions

This repository contains a GitHub action which automatically builds and published docker images after a release inside the repository gets published. These images get pushed to the GitHub Container Repository. However, this means that you have to adjust the credentials used for this action if you want to publish your own Docker images. To do so just follow these steps:

tip

You could also just completely remove the action. In this case you have to make sure to not commit the removed action file in any PRs made to the parent repository!

Generate a new Personal Access Token (PAT) and copy it for the next step. Make sure you follow the guidelines in the official GitHub guide for generating a PAT for the Container Repository and to set the permission described there.

caution
The PAT has to belong to the user who owns the repository!
Add the PAT as a secret to your fork and name it GH_REGISTRY_TOKEN. Go to Settings > Secrets on your repository page to do so. If you change the name of this token you have to follow the next step aswell.

(Only if you changed the name of the token) Replace the GH_REGISTRY_TOKEN name inside the workflow file (.github/workflows/build-push-docker.yml) in the login step to your name.

# Login to repository
- name: Login to DockerHub
  uses: docker/login-action@v1
  with:
    registry: ghcr.io
    username: ${{ github.repository_owner }}
    password: ${{ secrets.GH_REGISTRY_TOKEN }}

Update the name of the docker image to match the current repository. Replace {REPO_OWNER} inside the workflow file (.github/workflows/build-push-docker.yml) with the actual owner of your fork.

- name: Build and push the image
  uses: docker/build-push-action@v2
  with:
        push: true
        no-cache: true
        tags: |
        ghcr.io/{REPO_OWNER}/tutor-management-system:${{ github.event.release.tag_name }}
        ghcr.io/{REPO_OWNER}/tutor-management-system:latest

Update GitHub Actions​

Update GitHub Actions