fix: remove pull_request_review from dispatch-review condition - #6
Conversation
Prevents review bot feedback loop where each bot review triggers another dispatch-review, causing infinite re-reviews on the same SHA.
There was a problem hiding this comment.
Review: #6
Head SHA: f83d8ef
Timestamp: 2026-04-23T00:00:00Z
Outcome: approve
Summary
This is a correct, minimal fix for a review-bot feedback loop. The change removes github.event_name == 'pull_request_review' from the dispatch-review job's if condition, which prevents the bot's own review submissions from re-triggering the dispatch-review pipeline. The pull_request_review trigger is intentionally retained in the top-level on: block for future use by a planned fix agent. The YAML syntax, multi-line expression structure, and remaining conditions are all correct after the deletion.
Findings
Critical
None.
High
None.
Medium
None.
Low
None.
Info
- [style/conventions]
.github/workflows/fullsend.yaml— Thepull_request_reviewevent remains in theon:trigger block (line 21-22) but no job currently matches on it. This means GitHub will fire the workflow on review submissions and all jobs will be skipped. This is intentional per the PR description (reserved for a future fix agent), but worth tracking — if the fix agent is not added, consider removing the unused trigger to avoid unnecessary workflow runs.
Footer
Outcome: approve
This review applies to SHA f83d8efd775980ca9099c7d545d617649f37390c. Any push to the PR head clears this review and requires a new evaluation.
Summary
pull_request_reviewfrom thedispatch-reviewjob'sifconditionpull_request_reviewon:trigger for a future fix agentProblem
Review bot feedback loop: each bot review triggers another dispatch-review, causing infinite re-reviews on the same SHA. See fullsend-ai/fullsend#379.
🤖 Generated with Claude Code