fix: render banner at 2x for retina clarity

[shenxianpeng]

Problem

The profile banner (banner-light.png / banner-dark.png) looked soft/blurry on the org profile. The PNGs were rasterized at 1280×320, but GitHub displays them at roughly half that width — and on retina (2×) displays the browser then has to upscale ~2×, which is what makes the text look fuzzy.

Fix

Re-rendered both banners from the SVGs (source of truth) at 2560×640 (2×) with rsvg-convert:

rsvg-convert -w 2560 -h 640 -o banner-light.png banner-light.svg
rsvg-convert -w 2560 -h 640 -o banner-dark.png banner-dark.svg

• SVGs unchanged (still 1280×320 canvas — content coordinates stay as designed)
• Montserrat SemiBold installed locally so the COMMIT wordmark renders with the correct font
• Verified the render: same palette (#2c9ccd blue), same element layout, checkmarks render correctly
• branding/README.md updated: notes the 2× raster size and documents the render command so future re-renders don't regress to 1×
• profile/README.md needs no change — it points at branding/banner-*.png, so the new files are picked up automatically

Before / after check

The profile page now displays the banner at its native resolution on retina screens instead of upscaling.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 48 minutes

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

Review profile: CHILL

Plan: Pro Plus

Run ID: 512b7ecf-06a9-48f0-b701-8ab60a98d191

📥 Commits

Reviewing files that changed from the base of the PR and between c80ee48 and e672bd8.

⛔ Files ignored due to path filters (2)

• branding/banner-dark.png is excluded by !**/*.png
• branding/banner-light.png is excluded by !**/*.png

📒 Files selected for processing (1)

• branding/README.md

---

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

[github-actions]

Commit-Check ✔️