Skip to content

fix: Green Void popup does not open after dismissing Minecraft popup …#64

Merged
creatorcluster merged 1 commit into
creatorcluster:mainfrom
Coder-soft:main
Jul 7, 2026
Merged

fix: Green Void popup does not open after dismissing Minecraft popup …#64
creatorcluster merged 1 commit into
creatorcluster:mainfrom
Coder-soft:main

Conversation

@Coder-soft

Copy link
Copy Markdown

…in same session

@vercel

vercel Bot commented Jul 7, 2026

Copy link
Copy Markdown

@Coder-soft is attempting to deploy a commit to the yamura3's projects Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Jul 7, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 56 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0880055b-3848-47cb-9175-4f26c1fef7fe

📥 Commits

Reviewing files that changed from the base of the PR and between 8447899 and 6b51da5.

📒 Files selected for processing (2)
  • src/components/resources/GreenVoidPopup.tsx
  • src/components/resources/MinecraftChangelogPopup.tsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

@creatorcluster creatorcluster merged commit cb5ddd2 into creatorcluster:main Jul 7, 2026
2 of 4 checks passed
@greptile-apps

greptile-apps Bot commented Jul 7, 2026

Copy link
Copy Markdown

Greptile Summary

This PR lets the Green Void popup open after the Minecraft popup is dismissed in the same session. The main changes are:

  • Green Void now re-checks its localStorage gate on a custom window event.
  • Minecraft now dispatches that event after saving its dismissed state.
  • Both popups keep their existing dismissed-key behavior.

Confidence Score: 5/5

This looks safe to merge.

  • No blocking issues found in the changed code.

Important Files Changed

Filename Overview
src/components/resources/GreenVoidPopup.tsx Adds an event listener that re-runs the existing localStorage check and cleans it up on unmount.
src/components/resources/MinecraftChangelogPopup.tsx Dispatches the popup-dismissed event after writing the Minecraft dismissed key.

Reviews (1): Last reviewed commit: "fix: Green Void popup does not open afte..." | Re-trigger Greptile

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.

2 participants