-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Open
Labels
bugSomething isn't workingSomething isn't workingp2Non-showstopper bug or popular feature requestNon-showstopper bug or popular feature request
Description
Problem
When using claude-code-action in multiple parallel jobs within the same workflow (e.g., separate "Code Quality Review" and "Security Review" jobs), the PR comments overwrite each other. Only the last job's comment remains visible.
Expected Behavior
Each job should be able to post its own independent comment that persists, allowing for:
- Separate code quality review comment
- Separate security review comment
- Any other specialized review comments
Current Behavior
When two jobs run in parallel:
jobs:
code-review:
steps:
- uses: anthropics/claude-code-action@v1
with:
prompt: "Review code quality..."
security-review:
steps:
- uses: anthropics/claude-code-action@v1
with:
prompt: "Review security..."The second job's comment overwrites the first one, resulting in only one visible comment.
Attempted Workarounds
- Using
use_sticky_comment: false- Comments still collide - Using
marocchino/sticky-pull-request-commentwith differentheadervalues - Doesn't work becauseclaude-code-actionposts its own comment regardless - Combining prompts into single job - Works but loses the benefit of parallel execution and separate concerns
Proposed Solutions
- Add a
comment_idorcomment_headerparameter to differentiate comments from different jobs - Support for custom comment posting (disable built-in commenting, expose result as output only)
- Built-in support for multiple review types with separate comments
Environment
- Action version: v1
- Workflow trigger: pull_request
Use Case
We want to run specialized reviews in parallel:
- Code quality review
- Security review (SQL injection, auth issues, etc.)
Each review has different prompts and should produce separate, persistent comments.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingp2Non-showstopper bug or popular feature requestNon-showstopper bug or popular feature request