Stacked PR checks unrelated to the topmost PR are skipped
还没有人认领这个 Issue。
评估
调研方向
首先追踪已发布 stack 的 CI workflows 是如何被选择的，并使用两个影响仓库中互不相关区域的堆叠 PR 重现该问题。完成标准是 stack 中的每个 PR 都运行与其自身更改相关的 workflows，包括在最上层 PR 未触发这些 workflows 时运行较低层的 PR。
由索引模型根据 Issue 内容生成。
描述
What happened
For a stack of pull requests, CI workflows are skipped when they are unrelated to the topmost PR in the stack, even if they are relevant to a lower PR.
Reproduction
- Configure separate CI workflows that run for changes to different parts of the repository.
- Create PR A from the trunk branch with a change that should trigger one of those workflows.
- Create PR B on top of A with an unrelated change that does not trigger that workflow.
- Publish A and B as a stack.
- Observe that the workflow relevant to PR A is skipped because it is unrelated to the topmost PR, PR B.
Expected behavior
Each PR in the stack should run the CI workflows relevant to its own changes.
Actual behavior
CI workflows are selected based on the topmost PR in the stack. Workflows unrelated to that PR are skipped across the stack, including workflows that are relevant to lower PRs.
Example consequence
PR A changes a database migration and should trigger migration tests. PR B adds an unrelated application change on top. If the migration workflow is unrelated to PR B, it is skipped, leaving PR A without the CI coverage relevant to its changes.
This is distinct from #319, where stale or missing merge refs prevent pull request workflows from running at all.
- 主要语言
- Go
- 星标
- 1.5k
- 派生
- 73
- 平均合并
- 1 天 8 小时
- 30 天内合并 PR
- 7
贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
github/gh-stack 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 85/100
-
难度 1/5 1 小时以内 新手友好度 92/100
-
feature request topic: cli - general
难度 2/5 1-3 小时 新手友好度 68/100
-
feature request topic: auto-merge
难度 2/5 1-3 小时 新手友好度 68/100
-
bug topic: docs
难度 1/5 1 小时以内 新手友好度 68/100
相似的 Issue
-
textual definition
难度 1/5 1 小时以内 新手友好度 90/100
geneontology/go-ontology#32653 ·
-
难度 1/5 1 小时以内 新手友好度 75/100
-
needs design
难度 2/5 1-3 小时 新手友好度 75/100
-
Priority/High ready-for-agent Severity/Major Type/Bug
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 2/5 1-3 小时 新手友好度 70/100