Skip to content

Conversation

@2sem
Copy link
Owner

@2sem 2sem commented Jan 16, 2026

disable claude code review
to review by gemini

@github-actions
Copy link

🤖 Hi @2sem, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

## 📋 Review Summary

This Pull Request successfully disables the Claude code review workflow in favor of Gemini. The changes are minimal, safe, and correctly handle the transition to comment-based triggers (even though the job is currently disabled).

🔍 General Feedback

  • The use of if: false is a clean way to temporarily disable the automation without deleting the configuration.
  • Trigger and PR number logic updates are well-implemented and compatible with GitHub's event structure for issues and pull requests.

# github.event.pull_request.user.login == 'new-developer' ||
# github.event.pull_request.author_association == 'FIRST_TIME_CONTRIBUTOR'

if: false

Choose a reason for hiding this comment

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

🟢 Using `if: false` is a simple and effective way to disable the job while keeping the configuration intact for future use. Note that the workflow will still trigger on the specified events but will be marked as skipped in the Actions tab.

REPO: ${{ github.repository }}
PR NUMBER: ${{ github.event.pull_request.number }}
PR NUMBER: ${{ github.event.pull_request.number || github.event.issue.number }}

Choose a reason for hiding this comment

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

🟢 This logic robustly handles different event types. Specifically, `issue_comment` on a Pull Request uses `github.event.issue.number`, while `pull_request` and `pull_request_review` events use `github.event.pull_request.number`.

@2sem 2sem merged commit bfae597 into master Jan 16, 2026
4 checks passed
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