This repository has been archived by the owner on Jul 14, 2024. It is now read-only.

Minor update (This remove some weird behaviour) #45

	name: Docker Image CI

	on:
	push:
	branches:
	- 'latest'
	- 'v[0-9]+.[0-9]+.[0-9]+'

	env:
	REGISTRY: ghcr.io
	IMAGE_NAME: ${{ github.repository }}

	jobs:
	build-and-push-image:
	runs-on: ubuntu-latest
	permissions:
	contents: read
	packages: write
	steps:
	- name: Checkout repository
	uses: actions/checkout@v4
	- name: Log in to the Container registry
	uses: docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1
	with:
	registry: ${{ env.REGISTRY }}
	username: ${{ github.actor }}
	password: ${{ secrets.GITHUB_TOKEN }}
	- name: Extract metadata (tags, labels) for Docker
	id: meta
	uses: docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7
	with:
	images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
	# This step uses the `docker/build-push-action` action to build the image, based on your repository's `Dockerfile`. If the build succeeds, it pushes the image to GitHub Packages.
	# It uses the `context` parameter to define the build's context as the set of files located in the specified path. For more information, see "[Usage](https://github.com/docker/build-push-action#usage)" in the README of the `docker/build-push-action` repository.
	# It uses the `tags` and `labels` parameters to tag and label the image with the output from the "meta" step.
	- name: Build and push Docker image
	uses: docker/build-push-action@f2a1d5e99d037542a71f64918e516c093c6f3fc4
	with:
	context: .
	push: true
	tags: ${{ steps.meta.outputs.tags }}
	labels: ${{ steps.meta.outputs.labels }}

Provide feedback