chore(ci): remove upstream branch-checks.yml with NVIDIA self-hosted runners#2
Merged
Merged
Conversation
…runners The branch-checks.yml workflow was inherited from NVIDIA/OpenShell and uses self-hosted runner labels (build-amd64, build-arm64) and a private NVIDIA container image (ghcr.io/nvidia/openshell/ci:latest) that do not exist in the kagenti fork. All 6 jobs queue indefinitely waiting for runners that will never appear. The equivalent checks (Rust, Python, Markdown) are already covered by kagenti-ci.yml using ubuntu-latest runners and pass correctly. Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com> Signed-off-by: Paolo Dettori <dettori@us.ibm.com>
huang195
added a commit
that referenced
this pull request
Jun 26, 2026
…mages.sh Drop the manual "check out kagenti-extensions" prerequisite. When EXT_DIR is unset, the script now clones the placeholder-resolve plugin itself from EXT_REPO @ EXT_REF (default huang195/kagenti-extensions @ feat/placeholder-resolve-plugin; switch to canonical main once PR NVIDIA#626 merges). EXT_DIR still wins for a local checkout. The supervisor side needs no checkout step — it builds from this OpenShell repo (you're already on feat/authbridge-egress). - 01-build-images.sh: EXT_DIR optional; add EXT_REPO/EXT_REF; clone-or-reuse before the build; fail-fast message points at EXT_REPO/EXT_REF. - README + guide: prereq #2 is just the OpenShell branch; the plugin is cloned for you; drop the EXT_DIR export from the quick-start; document EXT_REPO/EXT_REF. Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com> Signed-off-by: Hai Huang <huang195@gmail.com>
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.
Summary
.github/workflows/branch-checks.yml, which was inherited from NVIDIA/OpenShell and hardcodes self-hosted runner labels (build-amd64,build-arm64) and a private NVIDIA container image (ghcr.io/nvidia/openshell/ci:latest) that do not exist in the kagenti forktotal_count: 0self-hosted runners registered)kagenti-ci.ymlusingubuntu-latestrunners, which pass correctlyRoot Cause
branch-checks.ymldepends on two NVIDIA-internal resources unavailable in the fork:build-amd64/build-arm64— no such runners registered inkagenti/OpenShellghcr.io/nvidia/openshell/ci:latest— NVIDIA's GHCR, not accessible from the forkGitHub queues these jobs but never schedules them, resulting in perpetual
pendingstatus on every PR.Assisted-By: Claude (Anthropic AI) noreply@anthropic.com