Clarify that pipeline-overrides don't have to be statically used to b… #2

	# Prepare the docker image that builds specs.
	name: build-push-custom-image

	on:
	push:
	branches: [ "main" ]
	paths:
	- "tools/custom-action/dependency-versions.sh"
	- "tools/custom-action/Dockerfile"
	- "tools/custom-action/entrypoint.sh"
	- "tools/custom-action/prepare.sh"
	# Allows admins to trigger the workflow manually from GitHub UI or CLI, anytime.
	workflow_dispatch:

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

	jobs:
	build:
	runs-on: ubuntu-22.04
	permissions:
	contents: read
	packages: write
	defaults:
	run:
	shell: bash

	steps:
	- uses: actions/checkout@v4

	- name: Set up QEMU
	uses: docker/setup-qemu-action@v3

	- name: Set up Docker Buildx
	uses: docker/setup-buildx-action@v3

	- name: Log in to the Container registry
	uses: docker/login-action@v3.0.0
	with:
	registry: ${{ env.REGISTRY }}
	username: ${{ github.actor }}
	password: ${{ secrets.GITHUB_TOKEN }}

	- name: Extract metadata (tags, labels) for Docker
	id: meta
	uses: docker/metadata-action@v5.3.0
	with:
	images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}

	- name: Build and push Docker image
	uses: docker/build-push-action@v5.1.0
	with:
	context: tools/custom-action
	platforms: linux/amd64,linux/arm64
	push: true
	tags: ${{ steps.meta.outputs.tags }}
	labels: ${{ steps.meta.outputs.labels }}

Provide feedback