Skip to content

Conversation

nikosdouvlis
Copy link
Member

@nikosdouvlis nikosdouvlis commented Aug 25, 2025

Description

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • Chores
    • Updated automated review configuration to omit certain CI versioning commit titles from auto-review checks, reducing noise and improving signal in PR reviews. This streamlines maintenance workflows and keeps reviewer attention on meaningful changes. No impact on application features, performance, or user experience. No user action is required. Release functionality remains unchanged.

Copy link

changeset-bot bot commented Aug 25, 2025

⚠️ No Changeset found

Latest commit: 8b4eea9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Aug 25, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
clerk-js-sandbox Ready Ready Preview Comment Aug 25, 2025 9:36am

Copy link
Contributor

coderabbitai bot commented Aug 25, 2025

Walkthrough

Added an ignore_title_keywords entry under reviews.auto_review in .coderabbit.yaml to exclude the title keyword "ci(repo): Version packages" from auto-review title checks.

Changes

Cohort / File(s) Summary
CI Config
./.coderabbit.yaml
Added reviews.auto_review.ignore_title_keywords entry with value "ci(repo): Version packages".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I twitch my nose at titles long,
A carrot-colored tag in commit song.
Now auto-reviews hop past this phrase,
ci(repo) drifts through pipeline haze.
With gentle thumps I mark the tracks—
Versioned packages, fewer checks! 🥕🐇

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch nikos/coderabbit-config

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

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

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

pkg-pr-new bot commented Aug 25, 2025

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@6630

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@6630

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@6630

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@6630

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@6630

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@6630

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@6630

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@6630

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@6630

@clerk/express

npm i https://pkg.pr.new/@clerk/express@6630

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@6630

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@6630

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@6630

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@6630

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@6630

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@6630

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@6630

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@6630

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@6630

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@6630

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@6630

@clerk/types

npm i https://pkg.pr.new/@clerk/types@6630

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@6630

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@6630

commit: 8b4eea9

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (3)
.coderabbit.yaml (3)

3-4: Broaden skipping logic to cover common release-PR title variants.

Relying on a single literal keyword may miss bot-generated titles that vary slightly across time or tooling (e.g., different casing or scope such as “ci(changesets): version packages”). Since matching is substring + case-insensitive, consider adding a few safe variants and/or an author/label guard for better recall.

Apply this diff to add common variants:

 reviews:
   auto_review:
     ignore_title_keywords:
       - 'ci(repo): Version packages'
+      - 'ci(repo): version packages'
+      - 'ci(changesets): version packages'
+      - 'version packages'

Notes:

  • Adding the generic 'version packages' is convenient but broader. If you worry about false positives, omit that line and rely on the two explicit variants instead.

---

`1-4`: **Add secondary guards: ignore known bot authors and/or a negative label filter.**

If your release PRs are authored by a bot, using ignore_usernames is robust against future title changes. A negative label filter also works if you consistently label release PRs (e.g., “release”).

Proposed diff:

```diff
 reviews:
   auto_review:
     ignore_title_keywords:
       - 'ci(repo): Version packages'
+    ignore_usernames:
+      # Replace with the actual bot usernames used in this repo
+      - 'changeset-release-bot'
+      - 'github-actions[bot]'
+    labels:
+      # Review all PRs except those carrying the release label
+      - '!release'

Caveats:

  • The labels array is inclusive by default; including only a negative label like '!release' keeps reviews on for all PRs except those labeled 'release'. Ensure your workflow reliably applies that label to release PRs.

---

`1-4`: **Release PR title and author verification complete**  

- **Location:** `.coderabbit.yaml` (lines 1–4)  
- All recent release PRs in `clerk/javascript` (the last 50+) use the exact title `ci(repo): Version packages` and are authored by `clerk-cookie`.  
- There is no single stable label applied to these PRs, so the title pattern is the most reliable signal.  

Optional enhancement (recommended): lock the author guard to `clerk-cookie` to further reduce false positives:

```diff
 reviews:
   auto_review:
     ignore_title_keywords:
       - 'ci(repo): Version packages'
+    require_author:
+      - 'clerk-cookie'
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 16f9f4e and 8b4eea9.

📒 Files selected for processing (1)
  • .coderabbit.yaml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (27)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (elements, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 14)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (machine, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (expo-web, chrome)
  • GitHub Check: Integration Tests (tanstack-react-router, chrome)
  • GitHub Check: Integration Tests (quickstart, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: Publish with pkg-pr-new
  • GitHub Check: Unit Tests (22, **)
  • GitHub Check: Static analysis
  • GitHub Check: Unit Tests (18, --filter=@clerk/astro --filter=@clerk/backend --filter=@clerk/express --filter=@c...
  • GitHub Check: Formatting | Dedupe | Changeset
  • GitHub Check: semgrep/ci
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (1)
.coderabbit.yaml (1)

1-4: LGTM: Schema-compliant YAML and correct placement under reviews.auto_review.

The structure matches the documented schema for reviews.auto_review.ignore_title_keywords and should successfully skip auto-reviews when titles contain the given keyword (case-insensitive).

@nikosdouvlis nikosdouvlis merged commit d2b41d5 into main Aug 25, 2025
40 of 41 checks passed
@nikosdouvlis nikosdouvlis deleted the nikos/coderabbit-config branch August 25, 2025 10:03
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