Skip to content

ci: type-check evals in pull request workflow - #92

Open
ANIRUDDHA ADAK (aniruddhaadak80) wants to merge 1 commit into
microsoft:mainfrom
aniruddhaadak80:fix/ci-typecheck-evals
Open

ANIRUDDHA ADAK (aniruddhaadak80) wants to merge 1 commit into
microsoft:mainfrom
aniruddhaadak80:fix/ci-typecheck-evals

Conversation

@aniruddhaadak80

@aniruddhaadak80 ANIRUDDHA ADAK (aniruddhaadak80) commented Sep 25, 2026 •

Copy link
Copy Markdown

Summary

Add the existing eval TypeScript project to the Ubuntu leg of the non-Windows workflow.

Why

The root TypeScript configuration excludes evals, while the existing test and build commands do not type-check that project. Eval type errors could therefore pass CI without running model-backed evals.

Changes

Testing

  • npm run typecheck:evals (new CI step; not executed yet)
  • npm test (existing CI command; not executed yet)
  • npm run build (existing CI command; not executed yet)

Local execution was not performed because this contribution is remote-only; no local checkout or source was used.

CI status

  • The first Non-Windows and Windows Actions runs are action_required with no jobs or logs; upstream workflow approval is required before the commands can run.
  • license/cla passed.
  • No npm result is claimed until an Actions run executes.

Fixes #6

Run the existing eval TypeScript project on the Ubuntu CI leg. The duplicate-run portion of microsoft#6 is intentionally unchanged because the current push trigger is already limited to main.

Fixes microsoft#6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CI: type-check evals in CI, and stop double-running the matrix on every PR

1 participant