Run init evals on CI
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github-actions
- Domain
- ci-cd, devops, testing-qa
Research direction
Start by reviewing test/init-eval/ and the previous workflow in commit d5d0b22, then determine how the Mastra server will be provided to CI. Add .github/workflows/init-eval.yml with the requested triggers, environment secrets, concurrency, and six-platform matrix; done means the eval suite runs successfully in CI.
Written by the indexing model from the issue text.
Description
Summary
Set up a CI workflow to run the test/init-eval/ eval suite automatically (on PRs and/or on a schedule).
Context
The eval tests exercise sentry init against real project templates and use an LLM judge to score correctness. They currently only run locally because they require a running Mastra API server.
The Mastra agent lives in https://github.com/getsentry/cli-init-api/.
Requirements
- Mastra server: Either deploy a persistent dev instance or spin one up as a service container in the workflow (pull from
getsentry/cli-init-api). - GitHub environment: Create an
init-evalenvironment with secrets:MASTRA_API_URL— URL of the Mastra serverOPENAI_API_KEY— for the LLM judge
- Workflow: Add
.github/workflows/init-eval.ymlwithpush/pull_request/workflow_dispatchtriggers. A previous version existed but was removed in d5d0b22 — can be used as a starting point. - Concurrency: Use a concurrency group to cancel in-progress runs on new pushes.
- Matrix: Run each platform (
express,nextjs,python-fastapi,python-flask,react-vite,sveltekit) as a separate matrix job withfail-fast: false.
Open questions
- Should the Mastra server be a persistent deployment (e.g. Cloudflare Worker) or spun up per-run?
- Should this run on every PR or only on a schedule / manual trigger to save costs?
- Dominant language
- TypeScript
- Stars
- 121
- Forks
- 14
- Avg merge
- 22h 3m
- Merged PRs (30d)
- 94
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getsentry/cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
bug jared
-
jared
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
safetrustcr/dApp-SafeTrust#426 ·
-
area:workflow bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fil-donadoni/tolaria#4409 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Fission-AI/OpenSpec#1960 ·
-
Add dependabot Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·