Infer base repository from parent branch in retarget/restack - #1749
Open
PawelLipski wants to merge 1 commit into
Open
Infer base repository from parent branch in retarget/restack#1749PawelLipski wants to merge 1 commit into
PawelLipski wants to merge 1 commit into
Conversation
PawelLipski
added
github
PawelLipski
force-pushed
the
fix/infer-base-repo-in-retarget-restack
branch
from
July 28, 2026 14:09
3f18f16 to
b1a2603
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #1749 +/- ##
========================================
Coverage 98.75% 98.75%
========================================
Files 45 45
Lines 5379 5388 +9
Branches 980 982 +2
========================================
+ Hits 5312 5321 +9
Misses 41 41
Partials 26 26 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
PawelLipski
force-pushed
the
fix/infer-base-repo-in-retarget-restack
branch
from
July 28, 2026 14:25
b1a2603 to
5f49498
Compare
In a fork workflow the PR/MR is hosted by the base (upstream) repository, not the head (fork) repository that holds the branches.
retarget-pr/restack-pr (and their GitLab retarget-mr/restack-mr counterparts) now resolve the code hosting client against the base repository
inferred from the parent branch's tracking remote - exactly like create-pr already does - so they query the repository that actually hosts the PR
even when no machete.{github,gitlab}.base* config keys are set.
Resolution is best-effort: if the base repository cannot be determined unambiguously and no base* keys are set, it falls back to the head repository,
preserving the previous behavior.
PawelLipski
force-pushed
the
fix/infer-base-repo-in-retarget-restack
branch
from
July 28, 2026 15:10
5f49498 to
85fbde1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In a fork workflow the PR/MR is hosted by the base (upstream) repository, not the head (fork) repository that holds the branches.
retarget-pr/restack-pr(and their GitLab retarget-mr/restack-mr counterparts) now resolve the code hosting client against the base repository inferred from the parent branch's tracking remote - exactly like create-pr already does - so they query the repository that actually hosts the PR even when nomachete.{github,gitlab}.base*config keys are set.Resolution is best-effort: if the base repository cannot be determined unambiguously and no
base*keys are set, it falls back to the head repository, preserving the previous behavior.