Skip to content

feat: GGUF export after LoRA merge#403

Open
Chirag7433 wants to merge 1 commit into
mainfrom
fix/patch-220
Open

feat: GGUF export after LoRA merge#403
Chirag7433 wants to merge 1 commit into
mainfrom
fix/patch-220

Conversation

@Chirag7433

Copy link
Copy Markdown
Collaborator

Maintenance patch 220.

@Chirag7433
Chirag7433 requested a review from SahilKumar75 as a code owner June 28, 2026 07:02

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated Review Checklist

Before approving this PR, confirm each item:

Code quality

  • Logic is correct and edge cases are handled
  • No debug logs, dead code, or commented-out blocks left in
  • Naming is clear — no abbreviations that need a comment to decode

Tests

  • New behaviour is covered by tests, or existing tests updated
  • poetry run pytest passes locally

Frontend (if applicable)

  • UI renders correctly across light/dark mode
  • No layout regressions on narrow viewports

Infrastructure / config (if applicable)

  • Secrets/env vars are not hardcoded
  • Docker build still passes (docker build .)

Docs

  • CHANGELOG or PR description explains the why, not just the what
  • Public API changes are reflected in docs

Review, check off what applies, then submit your formal Approve or Request Changes.

@github-actions github-actions Bot added the docs label Jun 28, 2026
@coderabbitai

coderabbitai Bot commented Jun 28, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@Chirag7433, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 38 minutes and 35 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7b637137-651c-49f2-b86a-ddb1bccc7d17

📥 Commits

Reviewing files that changed from the base of the PR and between 815a920 and fae7fb8.

📒 Files selected for processing (1)
  • CHANGELOG.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/patch-220

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.

@SahilKumar75 SahilKumar75 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Reviewed and approved.

@SahilKumar75 SahilKumar75 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants