Skip to content

fix: only repoint when target repo is explicitly known, propagate target via target_pr_repo#12

Open
dezren39 wants to merge 7 commits into
feat/pr-bodyfrom
feat/repoint-after-merge
Open

fix: only repoint when target repo is explicitly known, propagate target via target_pr_repo#12
dezren39 wants to merge 7 commits into
feat/pr-bodyfrom
feat/repoint-after-merge

Conversation

@dezren39
Copy link
Copy Markdown
Owner

@dezren39 dezren39 commented Apr 13, 2026

Part of a stack managed by ez.

Stack (this PR is 7 of 10):

  1. feat/config (rohoswagger#9)
  1. feat/worktree-ops (dezren39#2)
  2. feat/fork (dezren39#3)
  3. feat/local-merge (dezren39#4)
  4. feat/pr-body (dezren39#5)
  5. feat/repoint-after-merge ← you are here (dezren39#12)
  6. skill (dezren39#13)
  7. feat/ready-stack (dezren39#14)

…po PR repointing

Adds no_repoint boolean to StackState and BranchMeta with effective_no_repoint() resolution helper. Wired into config get/set (global and branch attrs). Resolution: per-branch > global > false.
…get via target_pr_repo

Two-part fix for incorrect auto-repoint after parent merge:

1. push.rs: Only trigger repoint when both current and target repos are Some and differ. The (Some, None) case no longer repoints, preventing spurious close-and-recreate when the target repo is unknown.

2. sync.rs: When cleaning up a merged parent, set target_pr_repo on children that already have PRs (instead of overwriting pr_repo). This preserves the actual PR location while signaling push where to repoint.

3. push.rs: Clear target_pr_repo after successful repoint to avoid stale hints.

4. Test helpers: Add target_pr_repo: None to all BranchMeta struct literals.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant