Getting Every PR in this stack has already been merged, when there is a PR already
- 主要言語
- Go
- スター
- 1.5k
- フォーク
- 70
- 平均マージ
- 1日 8時間
- マージ済み PR(30日)
- 7
説明
So I had branch 1 and branch 2 that created normally, and then branch3 was created while branch2 was in merge queue.
Then the git diff went weird but I fixed the merge conflicts, and thought maybe I'd try to `gh stack unstack`, but it didn't allow me because it was still part of the stack. Oh well, I continued on and tried making a PR for `branch4` and got this.
```
⚠ Every PR in this stack has already been merged on GitHub
Adding to a fully merged stack isn't supported — starting a new stack for your 2 unmerged branches based on master
Pushing to origin...
PR #52141 for branch3
✓ Created PR #52148 for branch4
✓ Stack created on GitHub with 2 PRs (stack #52149)
✓ Pushed and synced 2 branches
```
Everything looks good on the UI though
コントリビューションガイド
調査の方向性
Reproduce the sequence where branch3 is created while branch2 is in the merge queue, then run `gh stack unstack` and create a PR for branch4. Inspect the stack and PR creation flow to determine why it reports every PR as merged despite the resulting UI appearing correct. Done means the sequence no longer produces an inaccurate merged-stack warning or leaves the stack state inconsistent.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- github, go
- 領域
- cli
- issue の種類
- バグ
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 活発さ
- 静か
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 48/100