4 comments

  • caranlharris 5 hours ago ago

    My experience has made me more interested in seperating deterministic checks the judegment based reviews.Authentication changes have also taught me that passing inidividual checks doesnt mean an integration works end to end.

  • verdverm 12 hours ago ago

    Trigger a review agent for any commit which has an open PR and has passed build. Use open weights, or at minimum a different model family from the one which wrote the code. I will be publishing a write up soon(tm), inspired by but different from, cloudflare's post.

    I would napkin math the averaged cost per-review to be less than $1, which is less than our most rigorous validation pathway in CI (needs GPU for up to an hour). Time-wise around ~10-15m, with variability - and a bug in Argo with pod scheduling delays. This is fine because developers check in on their own PRs when they do and then make the changes that are needed. A key point here is that we are keeping humans in the loop in the PR.

    This is a large monorepo, I would expect much lower numbers for polyrepo setups.

    • easterncalculus 11 hours ago ago

      That's impressive! Would certainly read it when it comes out.

      • verdverm 11 hours ago ago

        teaser question, what parts of your agent PR process can you move to scripts?