feat: v0.2 batch — 6 issues (#106 #79 #85 #80 #74 #108)#112
Conversation
… TLS, progress (#106 #79 #85 #80 #74 #108) - #106: Add output footer watermark (terminal/SARIF/JSON) showing Cora version - #79: Remove blanket #![allow(dead_code)], targeted cleanup (27 warnings resolved) - #85: Add cargo-audit CI job for dependency CVE scanning - #80: Replace naive .gitignore parser with ignore crate (ripgrep-grade) - #74: Add REQUESTS_CA_BUNDLE env var support for corporate proxy TLS certs - #108: Add --progress flag for NDJSON stderr progress output Co-authored-by: CodeCora <codecora@users.noreply.github.com>
|
Warning Review limit reached
More reviews will be available in 32 minutes and 26 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughThis PR introduces structured progress reporting for ChangesProgress Reporting and Review Pipeline Enhancement
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related issues
Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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 |
🔍 Cora AI Code Review❌ Blocked — critical issues found. 🔴 Error (3)
Review powered by cora-cli · BYOK · MIT |
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
.github/workflows/ci.yml (1)
3-7:⚠️ Potential issue | 🔴 Critical | ⚡ Quick winWorkflow triggers violate coding guideline: missing push to
developbranch.The coding guideline requires CI/CD to run on push to the
developbranch, but the workflow currently only triggers on push tomain. This means commits pushed directly todevelopwill not be validated.📋 Proposed fix to add develop branch trigger
on: pull_request: branches: [develop] push: - branches: [main] + branches: [main, develop]As per coding guidelines: "CI/CD must run build, test, clippy, and fmt checks on push to
developbranch and on all PRs using the ci.yml workflow".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/ci.yml around lines 3 - 7, The workflow's triggers under the on: block only run push to main and misses pushes to develop; update the push trigger (the push key under on:) to include the develop branch so CI runs on pushes to develop as required by policy and still runs on PRs (pull_request). Locate the on: -> push configuration in ci.yml and add "develop" to the branches list so both main and develop are included.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/ci.yml:
- Around line 50-58: The CI job named "audit" currently uses the archived action
identifier actions-rs/audit-check@35b7b53b...; replace that uses entry with the
maintained rustsec action (rustsec/audit-check) and pin it to an immutable ref
(specific commit SHA) instead of the archived actions-rs one, preserving the
existing with: block (token: ${{ secrets.GITHUB_TOKEN }}) and the job name
"audit" and runs-on setting. Ensure the new action's inputs match the current
token usage and any required args from rustsec/audit-check.
In `@src/engine/scanner.rs`:
- Around line 72-77: WalkBuilder::new(root) currently enables
git_ignore/git_global/git_exclude but leaves the default require_git behavior,
so .gitignore files won't be honored outside a git repository; update the
WalkBuilder chain (the builder that calls hidden(), git_ignore(), git_global(),
git_exclude(), and build()) to explicitly call require_git(false) before build()
so .gitignore and global excludes are respected even when the root is not inside
a git repo.
---
Outside diff comments:
In @.github/workflows/ci.yml:
- Around line 3-7: The workflow's triggers under the on: block only run push to
main and misses pushes to develop; update the push trigger (the push key under
on:) to include the develop branch so CI runs on pushes to develop as required
by policy and still runs on PRs (pull_request). Locate the on: -> push
configuration in ci.yml and add "develop" to the branches list so both main and
develop are included.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 8908b7da-8906-4d82-bd51-a1b1ae4b5df0
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (17)
.github/workflows/ci.ymlCargo.tomlsrc/commands/review.rssrc/config/providers.rssrc/engine/llm.rssrc/engine/review.rssrc/engine/scanner.rssrc/engine/types.rssrc/formatters/compact.rssrc/formatters/json_fmt.rssrc/formatters/pretty.rssrc/formatters/sarif.rssrc/git/diff.rssrc/git/files.rssrc/hook/install.rssrc/main.rssrc/progress.rs
💤 Files with no reviewable changes (1)
- src/config/providers.rs
…t(false) - Replace archived actions-rs/audit-check with rustsec/audit-check (official RustSec) - Add .require_git(false) to WalkBuilder for safe gitignore outside repos Co-authored-by: CodeCora <codecora@users.noreply.github.com>
Cora review CI failed on v0.2 PR (58K chars > 50K default limit). Added --max-diff-size flag to review command, set 200K in cora-review action. Co-authored-by: CodeCora <codecora@users.noreply.github.com>
The --max-diff-size flag won't work until v0.2 is released (CI uses v0.1.8). Instead, create a temp .cora-ci.yaml with hook.max_diff_size: 200000 and use CORA_CONFIG env var (supported since v0.1.x). Co-authored-by: CodeCora <codecora@users.noreply.github.com>
Cora review caught that tls_built_in_root_certs(false) disables ALL system roots. If the custom bundle is incomplete (e.g. only proxy cert), connections to upstream APIs fail. Fix: just add_root_certificate() on top of built-in certs instead of replacing them. Fixes cora review blocking issue on PR #112. Co-authored-by: CodeCora <codecora@users.noreply.github.com>
Summary
Batch implementation of 6 issues for v0.2 release.
Quick Wins
#![allow(dead_code)], targeted cleanup (27 warnings → 0)cargo-auditCI job for dependency CVE scanningMedium
ignorecrate (ripgrep-grade correctness)REQUESTS_CA_BUNDLEenv var support for corporate proxy TLS certsFeature
--progressflag for NDJSON stderr progress output (Termul/GUI prerequisite)Stats
src/progress.rs(399 lines)Summary by CodeRabbit
New Features
--progressflag to review command for structured progress updatesChores