chore(ci): remove synchronize trigger from Claude auto-review workflow

[Manabu-GT]

Summary

Updated the Claude Auto Review workflow to remove the synchronize event trigger, which fires on every commit push to a pull request.

Changes

• Removed synchronize from the pull request event types that trigger the workflow
• Workflow now only runs on: opened, ready_for_review, and reopened events

Rationale

This change reduces unnecessary workflow executions and API calls. The synchronize event triggers on every new commit pushed to a PR, which can lead to redundant reviews and increased costs. By removing it, reviews will only be triggered when:

• A PR is initially opened
• A PR is marked as ready for review
• A previously closed PR is reopened

This is a more efficient approach that still ensures code review coverage at critical points in the PR lifecycle.

https://claude.ai/code/session_01AYi5jxsAJ6XttXhduZGKWQ

Summary by CodeRabbit

• Chores
  • Updated pull request workflow triggers to refine when automated reviews are initiated.

[coderabbitai]

📝 Walkthrough

Walkthrough

Modified GitHub Actions workflow configuration to adjust pull request trigger events. The claude-review workflow now executes when pull requests are opened, marked ready for review, or reopened, but no longer runs on push events to existing pull requests.

Changes

Cohort / File(s)	Summary
GitHub Actions Configuration .github/workflows/claude-review.yml	Removed "synchronize" event from pull_request triggers, reducing workflow execution frequency to only opened, ready_for_review, and reopened events.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore(ci): remove synchronize trigger from Claude auto-review workflow' directly and accurately describes the main change: removing the synchronize event from the CI workflow trigger configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch claude/remove-synchronize-trigger-c3cST

---

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 and usage tips.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9c30ce421e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[github-actions]

Qodana for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions