fix(ci): remove PR trigger from release workflow to prevent duplicate execution - #191
Conversation
… execution The pull_request trigger was causing the workflow to run on both: 1. PR merge (pull_request event) 2. The resulting push to main (push event) This created duplicate executions. Now the workflow only triggers on push to main branch, which covers both direct pushes and PR merges. Removed: - pull_request trigger (lines 7-10) - Conditional PR merge logic in Release step The workflow now: - Triggers only on push to main - Runs semantic-release to update version files - Creates a release PR if changes are detected Co-Authored-By: Claude <noreply@anthropic.com>
📝 WalkthroughWalkthroughSimplifies the release workflow by removing PR merge event gating and conditional branching logic. The workflow now unifies all release steps under a single push-to-main path, eliminating the distinction between PR merge and push events while retaining semantic-release and PR automation. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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. Comment |
Summary
Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.