Participant/coderabbit

[rlunar]

Description

Adds CodeRabbit to the Valkey participants page, including its logo, website link, and details about the free OSS code review tier available to Valkey contributors and maintainers.

Issues Resolved

Closes #618

Check List

• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8aff9bf7-d23b-42bb-87f5-fe54a43b0816

📥 Commits

Reviewing files that changed from the base of the PR and between 8df9c32 and 42bcf90.

⛔ Files ignored due to path filters (1)

• static/img/coderabbit.svg is excluded by !**/*.svg

📒 Files selected for processing (2)

• README.md
• _data/participants.yml

Included review availability: Your plan includes up to 1 review per rolling hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The PR pins local builds to Zola 0.22.0, documents incompatibility with later Zola versions, cleans participant data whitespace, and adds CodeRabbit as a participant.

Changes

Site content updates

Layer / File(s)	Summary
Zola build guidance README.md	The local build instructions require Zola 0.22.0 and state that Zola 0.23 and later are unsupported.
Participant records _data/participants.yml	Existing participant entries have trailing whitespace removed. A CodeRabbit entry adds its Valkey link, logo metadata, and company description.

Assessment against linked issues

Objective	Addressed	Explanation
Add CodeRabbit as a Valkey participant with the requested company name, links, description, and logo metadata [#618]	✅

Suggested reviewers: stockholmux

Merge Risk: ⚪ Minimal · up to 42bcf

This localized participant-page update has no actionable merge-blocking risk remaining and is merge-ready after normal checks and review.

---

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

[greptile-apps]

Greptile Summary

Adds CodeRabbit to the participants directory with its logo, website link, and OSS review-tier description, and updates local build guidance to specify Zola 0.22.0. The participant data and SVG parsed successfully, the site built successfully with Zola 0.22.0, and browser checks confirmed that CodeRabbit is absent before the change and rendered correctly on both the participants page and homepage carousel after it. The documented Zola version matches the deployment workflow.

Confidence Score: 5/5

The change is safe to merge based on successful static, build, and browser validation.

No defects were found. Validation exercised YAML and SVG parsing, malformed-input rejection, Zola 0.22.0 builds for the base and changed revisions, generated markup, browser rendering of both participant surfaces, and consistency between the README and deployment configuration.

Files Needing Attention: No files need follow-up attention.

T-Rex Logs

What T-Rex did

• Ran the CodeRabbit static validation script against the base and PR revisions with Zola 0.22.0, and YAML and SVG inputs parsed correctly or were rejected when malformed, while both revisions built successfully and generated-page assertions passed.
• Executed Playwright-based UI checks by loading the generated base and PR sites; the base site lacked CodeRabbit while the PR site showed CodeRabbit with a loaded logo, correct link, and description on the participants page and homepage carousel.
• Compared the README and CI deployment guidance and confirmed both specify Zola version 0.22.0.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "docs: Pin Zola to 0.22.0 to avoid breaki..." | Re-trigger Greptile}