Conversation
thomshutt
force-pushed
the
push-to-ghcr
branch
from
ea476f3 to
f014648
Compare
Collaborator
|
@thomshutt looks good, but just to double-check:
|
Contributor
Author
|
@leszko No new credentials needed - the ones it uses are built in to Github I'll try your scope-test repo now for testing! |
Signed-off-by: Thom Shutt <[email protected]>
… repository Signed-off-by: Thom Shutt <[email protected]>
thomshutt
force-pushed
the
push-to-ghcr
branch
from
c408028 to
2e3f60b
Compare
Contributor
Author
|
Confirmed that the push works on this branch and is pullable on Runpod |
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
2 participants
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.
We've been hitting issues with pull rate limiting on Docker Hub, so adding GHCR as a second option.