You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Local CI requires four external prerequisites — Python 3.10+, Docker, act, and yq — but the eval identifies a "Prerequisite Fog" compound that makes first-run validation nearly impossible. The name "yq" is shared by at least three different tools (mikefarah/yq, kislyuk/yq, the Python pip package "yq"), and the README does not specify which one. A PyYAML fallback exists in cli/localci/utils/yq.py when yq is absent, meaning the wrong yq doesn't always fail — it silently degrades. No prerequisite verification command exists (no localci doctor equivalent). This ambiguity compounds with a six-layer configuration model — .localci.yml, image-registry.yml, GHA workflow YAML, Docker, act configuration, and the scoring algorithm's internal logic — whose interactions are not directly observable. A new user who struggles to install the right yq then cannot distinguish "installation is broken" from "configuration is wrong," because no runnable example exercises the full config → workflow → act → results path.
Repository: local-ci-test-system
Severity: Medium
Problem
Local CI requires four external prerequisites — Python 3.10+, Docker, act, and yq — but the eval identifies a "Prerequisite Fog" compound that makes first-run validation nearly impossible. The name "yq" is shared by at least three different tools (mikefarah/yq, kislyuk/yq, the Python pip package "yq"), and the README does not specify which one. A PyYAML fallback exists in
cli/localci/utils/yq.pywhen yq is absent, meaning the wrong yq doesn't always fail — it silently degrades. No prerequisite verification command exists (nolocalci doctorequivalent). This ambiguity compounds with a six-layer configuration model —.localci.yml,image-registry.yml, GHA workflow YAML, Docker, act configuration, and the scoring algorithm's internal logic — whose interactions are not directly observable. A new user who struggles to install the right yq then cannot distinguish "installation is broken" from "configuration is wrong," because no runnable example exercises the full config → workflow → act → results path.Acceptance Criteria
examples/directory with a minimal sample projectREADME.mdin examples/ with step-by-step validation instructionsImplementation Notes