Skip to content

Make ClawBench Braintrust publishing opt-in - #228

Closed
masnwilliams wants to merge 1 commit into
mainfrom
hypeship/clawbench-braintrust-opt-in
Closed

masnwilliams wants to merge 1 commit into
mainfrom
hypeship/clawbench-braintrust-opt-in

Conversation

@masnwilliams

@masnwilliams masnwilliams commented Oct 1, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

The ClawBench workflow stops publishing every run to Braintrust. The publish step now runs only when the BENCHMARK_PUBLISH_BRAINTRUST repository variable is true.

Why this is enough

The benchmark report is rendered from the Harbor job directories, not from Braintrust, so unpublished runs still get the same job summary and pull-request comment. The only thing they lose is the "Open the Braintrust experiment" link, which the report already omits when there is no publication file.

Changes

  • benchmark-clawbench.yml: if: vars.BENCHMARK_PUBLISH_BRAINTRUST == 'true' on Publish Braintrust experiment. Check benchmark execution now accepts a skipped publish as well as a successful one.
  • benchmarks/harbor/README.md: documents the variable. Local bun run benchmark:publish is unchanged.

Testing

actionlint passes on the workflow. I have not triggered a benchmark run.


Note

Low Risk
Workflow gating and documentation only; benchmark execution and reporting paths are unchanged when publishing is enabled.

Overview
ClawBench CI no longer publishes every benchmark run to Braintrust by default. The Publish Braintrust experiment step runs only when the repository variable BENCHMARK_PUBLISH_BRAINTRUST is true; job summaries and PR comments still come from Harbor job directories, so skipping publish only drops the Braintrust experiment link when no publication.json is produced.

The final Check benchmark execution gate now treats a skipped publish step as acceptable (success or skipped), so workflows can pass without Braintrust upload. benchmarks/harbor/README.md documents the opt-in variable for CI alongside the existing Braintrust credentials.

Reviewed by Cursor Bugbot for commit 5cfd910. Bugbot is set up for automated code reviews on this repo. Configure here.

@vercel

vercel Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
mcp Ready Ready Preview Oct 1, 2026 5:30pm UTC

@masnwilliams

Copy link
Copy Markdown
Collaborator Author

superseded, evals keep publishing

This branch was successfully deployed

1 active deployment
Preview — 5cfd9100 Deployed Oct 1, 2026 by vercel[bot]
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.

1 participant