Skip to content

feat(automation): run noema hourly NVIDIA NIM review repair - #1077

Open
seonghobae wants to merge 1 commit into
mainfrom
feat/noema-hourly-nvidia-nim-review-repair
Open

feat(automation): run noema hourly NVIDIA NIM review repair#1077
seonghobae wants to merge 1 commit into
mainfrom
feat/noema-hourly-nvidia-nim-review-repair

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

Summary

Add a thin hourly NVIDIA NIM review-repair caller for ContextualWisdomLab/noema at minute 19 against protected main.

The live noema queue is drafts only (ContextualWisdomLab/noema#404, ContextualWisdomLab/noema#403, ContextualWisdomLab/noema#71). Existing heartbeats scanned Clearfolio, DiskSage, and fast-mlsirm and never named noema.

The caller maps only PR_REVIEW_MERGE_TOKEN and OPENCODE_APPROVE_TOKEN, grants job-scoped id-token: write, and leaves NVIDIA_NIM_API_KEY on the reusable worker. It never introduces COPILOT_GITHUB_TOKEN.

Verification

  • coverage run -m pytest tests && coverage report --show-missing: 1122 passed, 100%
  • interrogate: 100%

Doctoring

docs/doctoring/noema-hourly-review-caller.md (APA 7th)

Add a thin minute-19 caller for ContextualWisdomLab/noema on
protected main. The live queue is drafts only. The caller maps only
established scheduler credentials, grants job-scoped OIDC, and leaves
NVIDIA_NIM_API_KEY on the reusable worker.
@seonghobae
seonghobae enabled auto-merge (squash) August 17, 2026 02:58
@cursor

cursor Bot commented Aug 17, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@coderabbitai

coderabbitai Bot commented Aug 17, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 22 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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 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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 9877c2db-ffe7-4046-aea8-3ba13091ebde

📥 Commits

Reviewing files that changed from the base of the PR and between c47afc2 and 9142fea.

📒 Files selected for processing (8)
  • .github/workflows/hourly-nvidia-nim-review-repair.yml
  • .github/workflows/noema-hourly-review-repair.yml
  • AGENTS.md
  • ARCHITECTURE.md
  • CHANGELOG.md
  • CLAUDE.md
  • docs/doctoring/noema-hourly-review-caller.md
  • tests/test_noema_hourly_review_caller.py

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.

❤️ Share

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.

1 participant