Skip to content

docs(home): add missing community providers to Available Adapters table - #101

Merged
julpayne merged 1 commit into
mainfrom
docs/update-homepage-provider-list
Aug 17, 2026
Merged

docs(home): add missing community providers to Available Adapters table#101
julpayne merged 1 commit into
mainfrom
docs/update-homepage-provider-list

Conversation

@julpayne

Copy link
Copy Markdown
Collaborator

Summary

  • Adds 6 missing community providers to the homepage "Available Adapters" table: DeepEval, Inspect AI, RAGAS, RULER, SWE-bench, and WildGuard
  • Updates the "Multi-framework" card text to list all supported frameworks
  • Aligns the homepage with what is currently available in eval-hub-contrib

Test plan

  • Verify the homepage renders correctly with the expanded table
  • Confirm provider names and descriptions match eval-hub-contrib adapter definitions

Made with Cursor

The homepage adapter table was missing 6 providers that are now in
eval-hub-contrib: DeepEval, Inspect AI, RAGAS, RULER, SWE-bench, and
WildGuard. Also updates the Multi-framework card text to list all
supported frameworks.

Assisted-by: Cursor
Signed-off-by: Julian Payne <julpayne@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@coderabbitai

coderabbitai Bot commented Aug 14, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 55 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: ff4dda73-2893-4434-bc03-ad6a3b06582d

📥 Commits

Reviewing files that changed from the base of the PR and between 2967698 and 5e87444.

📒 Files selected for processing (1)
  • src/content/docs/home.mdx

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.

@github-actions

Copy link
Copy Markdown
PR Preview Action v1.8.1

🚀 View preview at
https://eval-hub.github.io/pr-preview/pr-101/

Built to branch gh-pages at 2026-08-14 14:27 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

@gnaulak-redhat gnaulak-redhat left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM from my end. Just a Q/Comment.

Should we put a note that not all of these are RHOAI supported, but all here are expected to work with RHOAI ?

@julpayne
julpayne merged commit e897e10 into main Aug 17, 2026
4 checks passed
@julpayne
julpayne deleted the docs/update-homepage-provider-list branch August 17, 2026 13:05
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