fix(ci): diff origin/main...HEAD for rebase-based PRs #360
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
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
thwap/steeper!360
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/358-ci-go-changes"
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?
What
Fix the CI
go-changesstep that was skipping Go tooling even when.gofiles were modified.Root cause:
git diff HEAD^1..HEAD^2fails on rebase-based PRs where HEAD is the branch tip, not a merge commit.Fix:
git fetch origin main && git diff --name-only origin/main...HEADwhich works correctly for all rebase branches.Testing
Closes #358
Review
Result: Approved — no issues. Closes #358.
Summary: Reverts PR #359's
HEAD^1..HEAD^2approach (broken on rebase PRs — no merge commit). Restoresgit fetch origin main+git diff --name-only origin/main...HEADwhich correctly uses the three-dot merge-base comparison for rebase-based branches. This is the correct fix — the original PR #335 had the right approach, PR #359's change was incorrect.New commits pushed, approval review dismissed automatically according to repository settings
Re-Review
Result: Approved — no blocking issues. Closes #358.
Changes since previous review:
fetch-depth: 0to checkout step (fixes shallow clone)origin/maintoorigin/${{ github.event.pull_request.base.ref }}(dynamic, works for non-main base branches)2>/dev/null || echo ""(error-safe)echo "changed files: $FILES"for CI logsPrevious issue (rebase PRs) is now handled correctly.