df10c4692a
Fixes issue #641 where users were getting banned due to rapid successive Claude runs triggered by the synchronize event. Changes: - Add checkHumanActor call to agent mode's prepare() method to reject bot-triggered workflows unless explicitly allowed via allowed_bots - Update checkHumanActor to accept GitHubContext (union type) instead of just ParsedGitHubContext - Add concurrency protection to all PR review workflow examples to prevent multiple reviews running simultaneously on the same PR - Add tests for bot rejection/allowance in agent mode 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
80 lines
2.7 KiB
YAML
80 lines
2.7 KiB
YAML
name: PR Review with Progress Tracking
|
|
|
|
# This example demonstrates how to use the track_progress feature to get
|
|
# visual progress tracking for PR reviews, similar to v0.x agent mode.
|
|
|
|
on:
|
|
pull_request:
|
|
types: [opened, synchronize, ready_for_review, reopened]
|
|
|
|
# Prevent multiple reviews from running simultaneously on the same PR
|
|
concurrency:
|
|
group: claude-review-${{ github.event.pull_request.number }}
|
|
cancel-in-progress: true
|
|
|
|
jobs:
|
|
review-with-tracking:
|
|
runs-on: ubuntu-latest
|
|
permissions:
|
|
contents: read
|
|
pull-requests: write
|
|
id-token: write
|
|
steps:
|
|
- name: Checkout repository
|
|
uses: actions/checkout@v5
|
|
with:
|
|
fetch-depth: 1
|
|
|
|
- name: PR Review with Progress Tracking
|
|
uses: anthropics/claude-code-action@v1
|
|
with:
|
|
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
|
|
|
|
# Enable progress tracking
|
|
track_progress: true
|
|
|
|
# Your custom review instructions
|
|
prompt: |
|
|
REPO: ${{ github.repository }}
|
|
PR NUMBER: ${{ github.event.pull_request.number }}
|
|
|
|
Perform a comprehensive code review with the following focus areas:
|
|
|
|
1. **Code Quality**
|
|
- Clean code principles and best practices
|
|
- Proper error handling and edge cases
|
|
- Code readability and maintainability
|
|
|
|
2. **Security**
|
|
- Check for potential security vulnerabilities
|
|
- Validate input sanitization
|
|
- Review authentication/authorization logic
|
|
|
|
3. **Performance**
|
|
- Identify potential performance bottlenecks
|
|
- Review database queries for efficiency
|
|
- Check for memory leaks or resource issues
|
|
|
|
4. **Testing**
|
|
- Verify adequate test coverage
|
|
- Review test quality and edge cases
|
|
- Check for missing test scenarios
|
|
|
|
5. **Documentation**
|
|
- Ensure code is properly documented
|
|
- Verify README updates for new features
|
|
- Check API documentation accuracy
|
|
|
|
Provide detailed feedback using inline comments for specific issues.
|
|
Use top-level comments for general observations or praise.
|
|
|
|
# Tools for comprehensive PR review
|
|
claude_args: |
|
|
--allowedTools "mcp__github_inline_comment__create_inline_comment,Bash(gh pr comment:*),Bash(gh pr diff:*),Bash(gh pr view:*)"
|
|
|
|
# When track_progress is enabled:
|
|
# - Creates a tracking comment with progress checkboxes
|
|
# - Includes all PR context (comments, attachments, images)
|
|
# - Updates progress as the review proceeds
|
|
# - Marks as completed when done
|