diff options
| author | DanConwayDev <DanConwayDev@protonmail.com> | 2026-02-26 16:35:59 +0000 |
|---|---|---|
| committer | DanConwayDev <DanConwayDev@protonmail.com> | 2026-02-26 16:35:59 +0000 |
| commit | 01aeb2a3265bcafa162987c85dd281981770bba7 (patch) | |
| tree | 76fe39f85d24a68586bdc282088b11474e3751d4 /src/bin/git_remote_nostr/fetch.rs | |
| parent | 54f0542a27e4ccab459d87283e4668d865ddd2bb (diff) | |
fix: correct merge-base in PR events from git push of pr/ branch
When pushing a pr/ branch, the ahead slice is reversed by callers before
being passed to generate_patches_or_pr_event_or_pr_updates, making it
oldest-first. The tip/first_commit assignments were backwards (using
first()/last() as if the slice were youngest-first), so the merge-base
was computed as the parent of the PR tip rather than the parent of the
oldest commit. Multi-commit PRs therefore showed only 1 commit when
applied via ngit apply.
Adds an integration test that pushes a two-commit large-file PR branch
and asserts the merge-base tag equals the main branch tip.
Diffstat (limited to 'src/bin/git_remote_nostr/fetch.rs')
0 files changed, 0 insertions, 0 deletions