You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would be nice if the image registry target(GHCR, DockerHub) can be automatically selected based on the image-repo-name. For example:
image-repo-name "ghcr.io/wearefrank" would target GHCR
image-repo-name "docker.io/wearefrank" would target DockerHub
image-repo-name "wearefrank" would default to GHCR???
I think GHCR would make a more sensible default than DockerHub, because DockerHub always requires secrets to be configured, while GHCR can use the default GitHub provided GH_TOKEN/GITHUB_TOKEN if permission is configured in repo setting.
image-repo-name is used by multiple resuable workflows and GitHub actions in this ci-cd-templates repository. They currently specifically require the ghcr.io/docker.io prefix to NOT be included. Most of the work will be to change those workflows/actions to handle image-repo-name with a registry prefix.
The text was updated successfully, but these errors were encountered:
Would be nice if the image registry target(GHCR, DockerHub) can be automatically selected based on the image-repo-name. For example:
I think GHCR would make a more sensible default than DockerHub, because DockerHub always requires secrets to be configured, while GHCR can use the default GitHub provided GH_TOKEN/GITHUB_TOKEN if permission is configured in repo setting.
image-repo-name is used by multiple resuable workflows and GitHub actions in this ci-cd-templates repository. They currently specifically require the ghcr.io/docker.io prefix to NOT be included. Most of the work will be to change those workflows/actions to handle image-repo-name with a registry prefix.
The text was updated successfully, but these errors were encountered: