Skip to content

feat(eval-image): measured Dockerfile and publish-eval-image workflow - #1

Open
echobt wants to merge 1 commit into
mainfrom
feat/eval-image-dockerfile-ci
Open

feat(eval-image): measured Dockerfile and publish-eval-image workflow#1
echobt wants to merge 1 commit into
mainfrom
feat/eval-image-dockerfile-ci

Conversation

@echobt

@echobt echobt commented Jul 26, 2026

Copy link
Copy Markdown
Contributor

Summary

Owns the measured ghcr.io/baseintelligence/agent-challenge-canonical image:

  • Reproducible Dockerfile (SOURCE_DATE_EPOCH, BuildKit named contexts for golden assets + agent-challenge tree)
  • workflow_dispatch publish workflow co-pinning AGENT_CHALLENGE_REF + GOLDEN_ASSETS_REF
  • Contract tests + docs (docs/eval-image.md)
  • Python 3.12 floor + lockfile

Test plan

  • CI green on this PR
  • Contract tests cover Dockerfile / workflow shape
  • First real publish still needs a golden-assets digest (ops follow-up)

Own the agent-challenge-canonical image build with ORAS golden-assets
named context, co-pinned AGENT_CHALLENGE_REF, and workflow_dispatch CI.
@coderabbitai

coderabbitai Bot commented Jul 26, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@echobt, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1c6759cb-4254-4f77-b990-597c7c028b8d

📥 Commits

Reviewing files that changed from the base of the PR and between 1cf65f9 and e9862ca.

⛔ Files ignored due to path filters (1)
  • uv.lock is excluded by !**/*.lock
📒 Files selected for processing (7)
  • .github/workflows/publish-eval-image.yml
  • .gitignore
  • Dockerfile
  • README.md
  • docs/eval-image.md
  • pyproject.toml
  • tests/test_eval_image_contract.py
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/eval-image-dockerfile-ci

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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