github / github/gh-stack

rebase: merging indirectly via combined branch does not rebase higher prs

未關閉
#407 0 則留言 4 個 reaction 已指派 0 人 在 GitHub 檢視
bug topic: post-merge rebase
主要語言
Go
星號
1.5k
分支
70
平均合併
1 天 8 小時
30 天內合併 PR
7

描述

BUG:

We create release branches that combine many PRs/branches into a single PR. When that PR is merged to the root the original PRs are closed as merged, BUT any stacked PRs do not rebase onto the root.

Repro:

1. Create three PRs A and B and C, with B stacked on A.
2. Create a third PR, D, which combines branches A and C.
3. Merge D onto master.
4. Observe that B is still stacked on A, and if branch A is deleted, PR B is auto closed.

貢獻指南

開啟貢獻指南

研究方向

No file, test, or entry point is named. Reproduce the A/B/C and combined D scenario, then trace the handling of merged pull requests and stacked-branch rebases; the fix is complete when B is rebased onto master after D merges and is not auto-closed when A is deleted.

由索引模型根據 Issue 內容生成。

評估

技術堆疊
git, github, go
領域
cli
Issue 類型
缺陷
難度
4/5
預估耗時
3-5 天
活躍度
冷清
描述清晰度
基本清楚
新手友好度
45/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。