Repository navigation
ci(ai-evals): Stop keeping eval outputs as artifacts - #375
Merged
Merged
Conversation
This repo is public, so the run-evals artifact (transcripts, products reports and the agent's workspace diff) was readable by anyone. The results still go to evals.sentry.dev.
Abdkhan14
approved these changes
Oct 20, 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
2 participants
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.
The AI Evals workflow kept each run's outputs as a GitHub Actions artifact. This repo is public, so anyone could download them. We want nothing from a run surfaced publicly, so this drops the artifact. The results still go to evals.sentry.dev, and the job log shows only pytest's progress and failures.
Testing: workflow-only change; the run-evals action already treats an empty artifact-name as no artifact.
🤖 Generated with Claude Code