Skip to content

docs: add JUnit to the homepage, and pin v2.20.4 - #81

Merged
shenxianpeng merged 4 commits into
mainfrom
chore/add-junit-to-users
Nov 10, 2026
Merged

shenxianpeng merged 4 commits into
mainfrom
chore/add-junit-to-users

Conversation

@shenxianpeng

@shenxianpeng shenxianpeng commented Nov 10, 2026 •

Copy link
Copy Markdown
Member

JUnit 5 runs the Commit Check Action on every pull request (Action v2.20.2, ai_attribution = forbid). This adds JUnit to the homepage "In the CI of" row, right after FreeBSD.

It also moves the pre-commit rev: pins from v2.20.2 to v2.20.4, the latest CLI release. The docs-sync check compares them against PyPI and was failing on main for that reason.

Before / after

Homepage users row, before and after

Built locally with mkdocs build --strict; pytest tests passes against commit-check 2.20.4. The screenshot file is added and removed again on this branch, so the squash merge only changes the docs pages.

@netlify

netlify Bot commented Nov 10, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for commit-check ready!

Name Link
🔨 Latest commit 35564a9
🔍 Latest deploy log https://app.netlify.com/projects/commit-check/deploys/6af3691a2462d3452d2d41be
😎 Deploy Preview https://deploy-preview-81--commit-check.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai

coderabbitai Bot commented Nov 10, 2026 •

Copy link
Copy Markdown

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

The landing page “In the CI of” list now includes a link to JUnit.

Changes: Landing page list

Layer / File(s) Summary
Add JUnit to the CI list
docs/index.md
The “In the CI of” list adds a link to JUnit.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: Minimal · up to 544b2

The JUnit listing adds no identified merge-blocking risk. CI currently reports stale version pins elsewhere.

Pre-merge checks: Passed 4

Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Title check Passed The title clearly identifies the JUnit homepage update. The reference to pinning v2.20.4 is not reflected in the changeset, so the title only partially describes the changes.
Finishing Touches

Generate unit tests (beta)

  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 1e3878dd-9e44-454a-8d93-e7d823b198dd
Commits

Reviewing files that changed from the base of the PR and between 7a4b812 and 544b2cc.

Files selected for processing: 1

  • docs/index.md

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

@shenxianpeng shenxianpeng self-assigned this Nov 10, 2026
@shenxianpeng shenxianpeng changed the title docs: add JUnit to the homepage users row docs: add JUnit to the homepage, and pin v2.20.4 Nov 10, 2026
@shenxianpeng
shenxianpeng merged commit 62054b3 into main Nov 10, 2026
8 checks passed
@shenxianpeng
shenxianpeng deleted the chore/add-junit-to-users branch November 10, 2026 18:58
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