redhat-actions/Push To Registry

Push a container image to an image registry

Trust Signals

Scorecard Score: Scorecard 4–6scored Jul 6, 2026
Maintenance Recency: Activelast commit Mar 30, 2026
License: MIT

Pinned Snippet

workflow.ymlSHA-pinned

uses: redhat-actions/push-to-registry@5ed88d269cf581ea9ef6dd6806d01562096bee9c # v2

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
image	Name of the image/manifest to push (e.g. username/imagename or imagename)	no	—
tags	'The tag or tags of the image/manifest to push. For multiple tags, separate by whitespace. For example, "latest v1"'	no	latest
registry	Hostname and optional namespace to push the image to (eg. quay.io/username or quay.io)	no	—
username	Username to use as credential to authenticate to the registry	no	—
password	Password to use as credential to authenticate to the registry	no	—
tls-verify	Verify TLS certificates when contacting the registry	no	true
digestfile	After copying the image, write the digest of the resulting image to the file. By default, the filename will be determined from the image and tag. The contents of this file are the digest output.	no	—
extra-args	Extra args to be passed to podman push. Separate arguments by newline. Do not use quotes - @actions/exec will do the quoting for you.	no	—

Outputs

name	description
digest	The pushed image/manifest digest, as written to the "digestfile"
registry-path	The first element of registry-paths.
registry-paths	A JSON array of registry paths to which the tag(s) were pushed