test: replace Docker Hub staging PAT usage#224
Open
crazy-max wants to merge 1 commit into
Open
Conversation
crazy-max
force-pushed
the
test-dockerhub-stage-rm
branch
from
e7d72cb to
6c6e867
Compare
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
crazy-max
force-pushed
the
test-dockerhub-stage-rm
branch
from
6c6e867 to
947f8d1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This replaces Docker Hub staging registry coverage in the github-builder test workflows with production Docker Hub test coverage.
The Docker Hub test jobs now push and verify
docker.io/dockereng/github-builder-testand the scoped auth coverage now uses GHCR.