content: publish latest to production (src/content → peanut-content@3c2d4cf) - #2730
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Included review availability: 2 reviews are currently available. Based on recent review activity, included reviews refill at 5 per hour. 📝 WalkthroughWalkthroughThe ChangesContent subproject
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: 🔵 Low · up to The PR updates the production content revision, but the referenced revision cannot currently be validated from the available checkout. Owner confirmation and content validation should be completed before automated merge; this is a bounded merge-readiness risk. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Code-analysis diffPainscore total: 7095.78 → 7095.78 (0) |
🧪 UI test report — ✅ all greenSuites
📊 Coverage (unit)
⏱ 10 slowest test cases
|
Auto-generated: bumps
src/contentto latest peanut-contentmain.Based on
main, so the diff is exactly the submodule pointer.content-publish-automerge.ymlapproves and merges this onceci-successis green. Anything other than a lonesrc/contentchange falls back to the normal 1-review gate.
Summary by CodeRabbit