Skip to content

fix: sync rebases branches with no unique commits#63

Merged
javoire merged 1 commit intomainfrom
jd/fix-sync-no-unique-commits
Feb 6, 2026
Merged

fix: sync rebases branches with no unique commits#63
javoire merged 1 commit intomainfrom
jd/fix-sync-no-unique-commits

Conversation

@javoire
Copy link
Owner

@javoire javoire commented Feb 6, 2026

Summary

  • Fix bug where stack sync skipped rebasing branches that had no unique commits by patch comparison
  • A branch with no unique patches can still be behind origin/master and need rebasing
  • Now performs rebase even when GetUniqueCommitsByPatch returns empty (rebase is a no-op if truly up-to-date)

🤖 Generated with Claude Code

When GetUniqueCommitsByPatch returns 0 commits, sync was returning early
without performing a rebase. This caused branches to remain behind
origin/master even though the output claimed success.

A branch can have no unique patches (e.g., all changes already merged,
or only merge commits which git cherry ignores) but still need rebasing
to incorporate new commits from the target.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@javoire javoire marked this pull request as ready for review February 6, 2026 20:07
@javoire javoire merged commit 525ab29 into main Feb 6, 2026
1 check passed
@javoire javoire deleted the jd/fix-sync-no-unique-commits branch February 6, 2026 20:07
javoire pushed a commit that referenced this pull request Feb 6, 2026
…026-02-06)

### Bug Fixes

* sync rebases branches with no unique commits ([#63](#63)) ([525ab29](525ab29))
@javoire
Copy link
Owner Author

javoire commented Feb 6, 2026

🎉 This PR is included in version 1.16.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant