Skip to content

feat(sync): support configurable remote for fork workflows#70

Merged
javoire merged 1 commit intomainfrom
fix-sync-no-unique-commits
Feb 26, 2026
Merged

feat(sync): support configurable remote for fork workflows#70
javoire merged 1 commit intomainfrom
fix-sync-no-unique-commits

Conversation

@javoire
Copy link
Owner

@javoire javoire commented Feb 26, 2026

Summary

  • Separates fetch remote from push remote in stack sync to support fork workflows where origin = fork and upstream = main repo
  • Base branches are fetched from the configurable remote while stack branches are still pushed to origin
  • Remote detection priority: CLI arg (stack sync upstream) > stack.fetchRemote git config > auto-detect upstream remote > origin

🤖 Generated with Claude Code

Separate fetch remote from push remote in `stack sync`. In fork
workflows where origin = fork and upstream = main repo, base branches
need to be fetched from upstream while stack branches are still pushed
to origin.

Remote detection priority: CLI arg > stack.fetchRemote config >
auto-detect upstream > origin.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@javoire javoire marked this pull request as ready for review February 26, 2026 21:48
@javoire javoire merged commit a2f292d into main Feb 26, 2026
1 check passed
@javoire javoire deleted the fix-sync-no-unique-commits branch February 26, 2026 21:48
javoire pushed a commit that referenced this pull request Mar 2, 2026
…026-03-02)

### Features

* **sync:** support configurable remote for fork workflows ([#70](#70)) ([a2f292d](a2f292d))

### Bug Fixes

* **sync:** skip branches checked out in other worktrees instead of aborting ([#71](#71)) ([fb0fd4f](fb0fd4f))
@javoire
Copy link
Owner Author

javoire commented Mar 2, 2026

🎉 This PR is included in version 1.19.0 🎉

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