Repository navigation
ci: register kilo eval workflows on main - #17
Merged
Merged
Conversation
GitHub Actions registers `workflow_dispatch` triggers from the default branch only. Until `manual-kilo-judge.yml` exists on `main`, it won't show up in the Actions tab and `gh workflow run` will refuse it — even when targeting the feature branch that holds the implementation. This is the small focused PR described in `docs/internal/adding-agent-eval-backend.md` §6, same shape as PR #12 (copilot) and PR #13 (codex). The file is copied verbatim from `feat/kilo-eval-backend` (PR #16). No code changes, no test changes, no doc changes. Safe to merge now: - `workflow_dispatch:` only — no push / pull_request / schedule triggers, so merging this PR cannot run anything on its own. - The job depends on skills-evals files (`kilo_driver.py`, `test_kilo_*.py`, the `X_X_AGENT_UNDER_TEST`-aware conftest) that don't exist on `main` yet. Dispatching against `main` would fail at the pytest step; the workflow is only meaningful when dispatched with `ref=feat/kilo-eval-backend`. - No new secrets. `DEEPSEEK_API_KEY` is already configured for the other manual-*-judge workflows. After merge: open Actions, pick "manual / kilo code <- llm judge", set **Use workflow from: feat/kilo-eval-backend**, and dispatch. Signed-off-by: Tanzim Saqib <[email protected]>
Mirrors the project-scope manual-kilo-judge.yml with X_X_INSTALL_SCOPE=user added so `x-x init` lands skills under ~/.kilo/skills/ instead of <workspace>/.kilo/skills/. Matches the existing claude/codex/copilot patterns where every backend ships both scope variants. Same merge-safety story as the project-scope file: workflow_dispatch only, depends on skills-evals files from feat/kilo-eval-backend (#16) that aren't on main yet, no new secrets. Signed-off-by: Tanzim Saqib <[email protected]>
tsaqib
added a commit
that referenced
this pull request
May 26, 2026
Mirrors the project-scope manual-kilo-judge.yml with X_X_INSTALL_SCOPE=user added so `x-x init` lands skills under ~/.kilo/skills/ instead of <workspace>/.kilo/skills/. Matches the existing claude/codex/copilot patterns where every backend ships both scope variants. Same file is being added to main via feat/kilo-workflows-only (#17) so the two PRs land identical content and don't conflict on merge. The user-scope conftest path was already wired in the previous commit on this branch — the workspace fixture reads X_X_INSTALL_SCOPE and logs the resolved skills dir under either .kilo/skills/ (project) or ~/.kilo/skills/ (user). No code change here, workflow file only. Signed-off-by: Tanzim Saqib <[email protected]>
This was referenced May 26, 2026
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
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.
Why this PR exists separately from #16
GitHub Actions only registers
workflow_dispatchtriggers from the default branch. Untilmanual-kilo-judge.ymlexists onmain, the Actions tab won't list it andgh workflow runwon't accept it — even against the feature branch that has the actual implementation. This is the small focused PR described indocs/internal/adding-agent-eval-backend.md§6, mirroring #12 (copilot) and #13 (codex).What's in the diff
One file, copied verbatim from the #16 feature branch:
.github/workflows/manual-kilo-judge.yml— project-scope kilo evalNo code changes. No test changes. No doc changes.
How to use after merge
feat/kilo-eval-backend(the branch in PR feat: add Kilo Code eval backend #16).actions/checkout@v6step will pull the feature branch's tree —kilo_driver.py, pytest cases, thekilorow inconstants.go, theX_X_AGENT_UNDER_TEST-aware conftest — and run against it.Dispatching against
maindirectly will fail: this branch still lacks the test files, thekilo_driver.pymodule, and thekilorow inconstants.go. That's the documented tradeoff.Safe to merge now
workflow_dispatch:only — nopush:/pull_request:/schedule:triggers. Merging this PR cannot run anything on its own.DEEPSEEK_API_KEYis already configured for the othermanual-*-judgeworkflows.Test plan
feat/kilo-eval-backend— smoke test should pass; scenario tests run the real DeepSeek-routed eval.References
kiloagent targetdocs/internal/adding-agent-eval-backend.md§6 — explains why this two-PR pattern is needed