chore: use ${{ github.repository_owner }} as repo for image pulls#1925
Conversation
…w 0.0.0-main tag as default On-behalf-of: Gerald Morrison (SAP) <gerald.morrison@sap.com> Signed-off-by: Gerald Morrison (SAP) <gerald.morrison@sap.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThree GitHub Actions workflows were modified to change hardcoded GHCR image references to use the repository owner variable and to adjust default image tags used by the conformance workflow. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs). Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/conformance.yml:
- Line 38: The default TOOLKIT_IMAGE value uses the tag '0.0.0-main' which isn't
published by the controller publisher (kubernetes-controller.yml publishes tags
like '0.0.0-${short_sha}'), causing standalone conformance runs to fail; update
the default TOOLKIT_IMAGE in conformance.yml to use the same short-SHA based
pattern (e.g., '0.0.0-${short_sha}' or a stable published tag) or change the
publisher in kubernetes-controller.yml to also publish '0.0.0-main' so both
naming schemes exist—adjust the TOOLKIT_IMAGE default or the publish step so
TOOLKIT_IMAGE, kubernetes-controller.yml, and conformance.yml agree on the tag
format.
In @.github/workflows/kubernetes-controller.yml:
- Line 173: The publish destination is hardcoded to ghcr.io/open-component-model
in the publish_latest job while toolkit_image uses ghcr.io/${{
github.repository_owner }}, causing mismatched owners; update the publish_latest
steps that build/push the controller image and chart (the steps producing the
chart and image artifacts and their push commands/arguments) to use ghcr.io/${{
github.repository_owner }} (or a reusable variable like repo_owner) instead of
ghcr.io/open-component-model so both the publish job and the toolkit_image
reference the same owner-aware registry string and forks publish/pull from the
same repository.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 53782d4e-128a-47f4-9ca0-a8e0d111872c
📒 Files selected for processing (3)
.github/workflows/cli.yml.github/workflows/conformance.yml.github/workflows/kubernetes-controller.yml
|
@morri-son do you wanna still incorporate the comments? |
…en-component-model#1925) On-behalf-of: Gerald Morrison (SAP) <gerald.morrison@sap.com> <!-- markdownlint-disable MD041 --> #### What this PR does / why we need it Instead of hard-coding `open-component-model` org, ${{ github.repository_owner }} should be used to enable testing on forks. The PR also changes the default tag for latest pushes to main to `0.0.0-main`. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated CI/CD workflow configurations with dynamic repository references and revised version tags. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Signed-off-by: Gerald Morrison (SAP) <gerald.morrison@sap.com> Co-authored-by: Gerald Morrison (SAP) <gerald.morrison@sap.com>
…en-component-model#1925) On-behalf-of: Gerald Morrison (SAP) <gerald.morrison@sap.com> <!-- markdownlint-disable MD041 --> #### What this PR does / why we need it Instead of hard-coding `open-component-model` org, ${{ github.repository_owner }} should be used to enable testing on forks. The PR also changes the default tag for latest pushes to main to `0.0.0-main`. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated CI/CD workflow configurations with dynamic repository references and revised version tags. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Signed-off-by: Gerald Morrison (SAP) <gerald.morrison@sap.com> Co-authored-by: Gerald Morrison (SAP) <gerald.morrison@sap.com> Signed-off-by: Gerald Morrison (SAP) <gerald.morrison@sap.com>
On-behalf-of: Gerald Morrison (SAP) gerald.morrison@sap.com
What this PR does / why we need it
Instead of hard-coding
open-component-modelorg, ${{ github.repository_owner }} should be used to enable testing on forks. The PR also changes the default tag for latest pushes to main to0.0.0-main.Summary by CodeRabbit