Skip to content

Update sponsor references for jdx.dev#178

Merged
jdx merged 3 commits into
mainfrom
codex/move-sponsors-to-jdx-dev
Jul 2, 2026
Merged

Update sponsor references for jdx.dev#178
jdx merged 3 commits into
mainfrom
codex/move-sponsors-to-jdx-dev

Conversation

@jdx

@jdx jdx commented Jul 2, 2026

Copy link
Copy Markdown
Owner

Summary

  • list Entire first in the README sponsor copy
  • point sponsor links at jdx.dev

Tests

  • git diff --check

Note

Low Risk
Documentation-only README changes with no runtime or security impact.

Overview
Updates the Sponsors section in README.md to name entire.io before 37signals and to send the “View all sponsors” link to https://jdx.dev/sponsors.html instead of https://en.dev/sponsors.html.

Reviewed by Cursor Bugbot for commit 2ae7c6f. Bugbot is set up for automated code reviews on this repo. Configure here.

@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 50 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: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 783fc3ed-ec92-4bfe-a6cf-976ac1972629

📥 Commits

Reviewing files that changed from the base of the PR and between 56cbe68 and 2ae7c6f.

📒 Files selected for processing (1)
  • 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

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

@greptile-apps

greptile-apps Bot commented Jul 2, 2026

Copy link
Copy Markdown

Greptile Summary

Updates the Sponsors section in README.md to explicitly name entire.io (listed first) and 37signals, and redirects the "View all sponsors" link from en.dev to jdx.dev.

  • Adds a sentence naming the two current sponsors, with entire.io listed before 37signals.
  • Updates the sponsor listing URL from https://en.dev/sponsors.html to https://jdx.dev/sponsors.html.

Confidence Score: 5/5

Pure documentation change with no runtime or logic impact — safe to merge.

Only README.md is touched: two lines add named sponsors and update a URL. No code paths, configurations, or tests are affected.

No files require special attention.

Important Files Changed

Filename Overview
README.md Adds named sponsor line (entire.io before 37signals) and updates "View all sponsors" link from en.dev to jdx.dev

Reviews (3): Last reviewed commit: "Limit repo sponsor callouts to premier s..." | Re-trigger Greptile

Comment thread README.md Outdated
@jdx jdx merged commit 78dfade into main Jul 2, 2026
8 checks passed
@jdx jdx deleted the codex/move-sponsors-to-jdx-dev branch July 2, 2026 18:34
@jdx jdx mentioned this pull request Jun 26, 2026
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.

1 participant