Wave-21 C04: commit signing policy and check - #180
Conversation
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Warning Review limit reached
Next review available in: 3 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (6)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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 |
Document GPG/SSH commit signing expectations, add machine-verifiable main-tip check with soft branch-protection checklist for OSS enforcement limits. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
02b86c5 to
82e33e0
Compare
| if ($Output -match 'No signature') { | ||
| return @{ Ok = $false; Detail = "no signature" } | ||
| } | ||
| if ($Output -match 'gpg:\s+Signature made|Good signature|not certified|Can''t check signature|no public key') { |
There was a problem hiding this comment.
WARNING: Test-CommitVerifier regex does not match SSH signature success output
The regex Good signature requires a literal space between Good and signature, but git verify-commit for SSH signatures outputs Good "git" signature for ... with quotes around git. Valid SSH signatures will be incorrectly reported as verification failures.
| if ($Output -match 'gpg:\s+Signature made|Good signature|not certified|Can''t check signature|no public key') { | |
| if ($Output -match 'gpg:\s+Signature made|Good "git" signature|not certified|Can''t check signature|no public key') { |
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| fetch-depth: 0 | ||
|
|
||
| - name: ensure origin/main is available on PR checkouts | ||
| run: git fetch --no-tags origin main |
There was a problem hiding this comment.
WARNING: git fetch --no-tags origin main fetches from origin, which for PRs from forks is the fork's main branch, not the upstream main
For cross-repo (fork) PRs, origin points to the fork. The script should fetch the upstream main explicitly so the tip check validates the correct branch.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
|
|
||
| on: | ||
| pull_request: | ||
| paths: |
There was a problem hiding this comment.
SUGGESTION: pull_request trigger has a paths filter that limits this workflow to run only when policy files change
The ADR and runbook state the check runs on every PR and main push, but the paths filter means most PRs will skip this workflow entirely. If the intent is to verify commit signing on every PR, remove the paths filter or add a separate lightweight workflow without it.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: 2 Warnings, 1 Suggestion Found | Recommendation: Request Changes Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (6 files)
Fix these issues in Kilo Cloud Reviewed by step-3.7-flash · Input: 93.4K · Output: 14.4K · Cached: 392.2K |
Summary
Test plan
Made with Cursor