Fix GHCR tag casing in runner-image workflow#48
Merged
Conversation
Docker repository names must be lowercase; github.repository_owner preserves the org's casing (CodingThrust), so the first run failed at tag validation. Compute the image namespace with tr in a dedicated step.
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.
The first
runner-image.ymlrun on main failed in 20s:github.repository_ownerpreserves the org's casing (CodingThrust); Docker repository names must be lowercase. This computes the image namespace viatrin a dedicated step and tagsghcr.io/codingthrust/problem-reductions-runner— matching theGHCR_IMAGEdefault in the Makefile.Same caveat as before: the workflow only fires on pushes to main, so this can only be fully verified by merging. The failure mode is deterministic (tag validation happens before any build), the fix is the standard lowercase-owner pattern, and YAML + the
trpipeline were verified locally.After merge, the first successful push still needs the one-time step: mark the GHCR package public (Packages → problem-reductions-runner → Package settings).