Skip to content

evidence(OMN-16229): OCC companion for OmniNode-ai/omnibase_infra#2794 - #6691

Merged
jonahgabriel merged 2 commits into
devfrom
jonah/omn-16229-occ-companion
Aug 19, 2026
Merged

jonahgabriel merged 2 commits into
devfrom
jonah/omn-16229-occ-companion

Conversation

@jonahgabriel

Copy link
Copy Markdown
Contributor

OCC Evidence-Source companion for OMN-16229 / OmniNode-ai/omnibase_infra#2794 (expiring-ignore policy for fix-unavailable CVEs in the Trivy image gate). Hand-authored per the standard manual-companion pattern (occ#6595 precedent). Self-bind entry to follow in a second commit once this PR's own number is known.

Evidence-Ticket: OMN-16229

Evidence-Source companion for the trivyignore-expiry PR. Self-bind
entry to follow in a second commit once this companion's own PR
number is known.
@coderabbitai

coderabbitai Bot commented Aug 18, 2026 •

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your current included review allowance is based on your included PR review attempts over the past 7 days.

Next review available in: 2 minutes

Limit details: You’ve used the included review currently available. Your 112 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 597755f4-c50e-4d58-8716-81affa289d93

📥 Commits

Reviewing files that changed from the base of the PR and between c1434d0 and 3637c25.

📒 Files selected for processing (4)
  • contracts/OMN-16229.yaml
  • drift/dod_receipts/OMN-16229/dod-OmniNode-ai-omnibase_infra-pr-2794/command.yaml
  • drift/dod_receipts/OMN-16229/dod-omnibase_infra-pr-2794-strict-gate/command.yaml
  • drift/dod_receipts/OMN-16229/occ-self-bind-pr-6691/command.yaml

Comment @coderabbitai help to get the list of available commands.

Adds the self-bind dod_evidence entry now that this companion's own
PR number is known.
@jonahgabriel jonahgabriel added the ci:ready Full CI runs on this PR (OMN-15731 label-gated CI pilot) label Aug 19, 2026
@jonahgabriel
jonahgabriel merged commit 3df4978 into dev Aug 19, 2026
165 of 172 checks passed
@jonahgabriel
jonahgabriel deleted the jonah/omn-16229-occ-companion branch August 19, 2026 07:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci:ready Full CI runs on this PR (OMN-15731 label-gated CI pilot)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant