Repository navigation
feat(cli): grade in map --json and a --baseline-label flag - #773
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
3 Skipped Deployments
|
|
Thank you for following the naming conventions! 🙏 |
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. 🧰 Additional context used📚 Code guidelines (4)No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (4)
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 1 remain after this review. 📝 WalkthroughWalkthroughThe map command accepts a custom label for a loaded baseline and includes the scan grade in JSON output. The CLI documentation link for GitHub format output now points to the CI page’s “without the action” section. ChangesMap CLI
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Feature Merge Risk: ⚪ Minimal · up to The change adds the requested baseline label and JSON grade behavior; no concrete merge-blocking risk is identified. Security Architecture ReviewSecurity architecture risk: 🔵 Low · up to The changes are limited to report data and baseline display names. The label does not select the baseline or control regression decisions, and GitHub annotations escape caller-controlled text. No material security concern was identified in the reviewed paths. Retained concerns Security review detailsSecurity Blast Radius
Trust Boundaries and Controls
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
@evlog/cli
evlog
@evlog/nuxthub
@evlog/signals
@evlog/telemetry
commit: |
79b00b6 to
4453204
Compare
Two follow-ups surfaced by
evloghq/action, which had to carry both itself.evlog map --jsoncarriesgrade(excellent/good/needs-work/poor) next tomapandsummary. The action recomputed it from the score thresholds, which drifts the day a threshold moves.--baseline-label <text>names the baseline in the report and in the--format githubannotations. The action scans the base branch into a temp file and passes it as--baseline, so the gate line readregressed against /tmp/evlog-base-x/….json; now it can sayregressed against main.Tests:
gradeasserted on the JSON payload; the regressions-only annotation test passes the label and asserts the gate line. Docs: flag row oncli/map. Changeset:@evlog/climinor.Summary by CodeRabbit
--baseline-labelto name the baseline in reports and GitHub-format annotations.--format githubdocumentation link.