Skip to content

fix: use push remote repo when creating PRs without explicit repo override#13

Open
dezren39 wants to merge 6 commits into
feat/repoint-after-mergefrom
skill
Open

fix: use push remote repo when creating PRs without explicit repo override#13
dezren39 wants to merge 6 commits into
feat/repoint-after-mergefrom
skill

Conversation

@dezren39
Copy link
Copy Markdown
Owner

@dezren39 dezren39 commented Apr 13, 2026

Part of a stack managed by ez.

Stack (this PR is 8 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 (dezren39#12)
  6. skill ← you are here (dezren39#13)
  7. feat/ready-stack (dezren39#14)

Implement undraft_stack_prs() in submit.rs that marks existing draft PRs ready for review when --no-draft is passed to submit. Add 17 new tests: 11 for submit (draft resolution, undraft integration with fake gh binary tracking log files, repo passthrough) and 6 for push (repoint guard: target_pr_repo hint priority, force flag, no-existing-repo skip, exact-match no-trigger, CLI override priority).
Previously force_repoint bypassed the repo mismatch check, meaning --repoint with matching repos would pointlessly close+recreate a PR. Now --repoint only overrides repoint=false config (the escape hatch) while still requiring actual repo mismatch. Adds force_repoint_does_not_trigger_when_repos_match test.
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