fix: Dont run on renovate #230
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
backend
ci
docs
frontend
lgtm
blocked
lgtm
done
lgtm
need 1
size
huge
size
large
size
medium
size
small
No milestone
No project
No assignees
2 participants
Due date
No due date set.
Dependencies
No dependencies set.
Reference: SZUT/casino#230
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "no-renovate"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The logic for skipping Renovate Bot commits has a critical flaw. The conditional check 'if: steps.check-renovate.outputs.author != Renovate Bot' references an undefined output since the check-renovate step doesn't set any outputs, only echoes and exits. Additionally, using 'exit 0' in line 25 will terminate the entire job, making the conditional check redundant.
Recommendation: Choose one approach - either remove the early exit and properly set outputs for the conditional, or remove the conditional and rely solely on the early exit. The current implementation mixes both approaches inconsistently.
b6ec777565
tocd43f111c4
-m LGTM! The changes successfully prevent Claude from running on Renovate Bot commits. The logic is sound and implementation is clean. Minor suggestion: consider using case-insensitive matching for 'renovate' in the author name to handle different bot naming conventions (e.g., 'renovate[bot]', 'Renovate Bot', etc.). The current exact string match works but could be more robust. Good work on the conditional execution approach!