Main

[Thejas775]

Description

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Build/CI changes

Related Issues

Fixes #

Checklist

• My code follows the code style of this project
• I have run ./gradlew spotlessApply to format my code
• I have run ./gradlew detekt and fixed any issues
• I have added tests that prove my fix is effective or that my feature works
• All new and existing tests passed
• I have updated the documentation accordingly
• I have added/updated KDoc comments for public APIs

Testing

• Unit tests pass on JVM
• Unit tests pass on Android
• Unit tests pass on iOS
• Manual testing performed

Screenshots (if applicable)

Additional Notes

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
pay-craft	Ready	Preview, Comment	Jul 14, 2026 12:34pm

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 54 minutes

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 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 3ef73340-afb0-4392-9941-5ebcdab928b9

📥 Commits

Reviewing files that changed from the base of the PR and between a63ec55 and 4fcf701.

📒 Files selected for processing (1)

• dashboard/next.config.js

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch main

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	paycraft-docs	4fcf701	Jul 14 2026, 12:37 PM