Skip to content

fix: comments number not updating is now updating mirroring the patte…#1044

Merged
coodos merged 1 commit into
mainfrom
fix/commentNumberNotUpdating
Jun 17, 2026
Merged

fix: comments number not updating is now updating mirroring the patte…#1044
coodos merged 1 commit into
mainfrom
fix/commentNumberNotUpdating

Conversation

@Sahil2004

Copy link
Copy Markdown
Contributor

…rn of likes.

Description of change

comments number not updating is now updating mirroring the pattern of likes.

Issue Number

Closes #1018

Type of change

  • Fix (a change which fixes an issue)

How the change has been tested

Manually.

Change checklist

  • I have ensured that the CI Checks pass locally
  • I have removed any unnecessary logic
  • My code is well documented
  • I have signed my commits
  • My code follows the pattern of the application
  • I have self reviewed my code

@Sahil2004 Sahil2004 self-assigned this Jun 17, 2026
@Sahil2004 Sahil2004 requested a review from coodos as a code owner June 17, 2026 10:29
@coderabbitai

coderabbitai Bot commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

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

More reviews will be available in 49 minutes and 34 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 refill rate.

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ca54299f-7846-4ea1-b1c2-8cf49ba50026

📥 Commits

Reviewing files that changed from the base of the PR and between 8890fad and 3c4af82.

📒 Files selected for processing (1)
  • platforms/pictique/client/src/lib/stores/comments.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/commentNumberNotUpdating

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 and usage tips.

@coodos coodos merged commit ce9b3d0 into main Jun 17, 2026
4 checks passed
@coodos coodos deleted the fix/commentNumberNotUpdating branch June 17, 2026 12:39
@talhaensomble96

Copy link
Copy Markdown

This issue is not fixed..

pull-1044.zip

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Pictique: New comment not visible until page is refreshed

3 participants