Ensure automated backport commits have verified signatures
维护者通常 1 天内回复
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 55/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- git, github, javascript
调研方向
Read .github/scripts/backport.js and the approach in NVIDIA/nvidia-container-toolkit PR #2012, then inspect the compatibility described in #2992. Verify both clean backports and conflict-resolved backports through backport CI. Done means generated commits report verified: true, preserve their trees and messages, and retain existing PR creation and conflict handling.
由索引模型根据 Issue 内容生成。
描述
The cherry-pick workflow currently creates backport commits locally and pushes them without signing. Recent automated backports report verified: false with reason unsigned, even when the original commits were signed.
This is incompatible with CI signature verification proposed in #2992 and branch protection requiring signed commits.
Update .github/scripts/backport.js to produce verified backport commits. Follow the approach implemented in nvidia-container-toolkit PR #2012:
- Recreate each cherry-picked commit through GitHub’s Git Data API, preserving its tree, message, and commit order.
- Update the backport branch to reference the resulting signed commit chain.
- Preserve existing PR creation and conflict-handling behavior.
This approach avoids managing a separate GPG or SSH signing key for the bot.
Acceptance criteria:
- GitHub reports verified: true for every generated backport commit.
- Backports preserve the expected changes and commit messages.
- Backport CI passes the signature-verification gate when enabled.
- Both clean backports and backports requiring manual conflict resolution remain supported.
- 主要语言
- Go
- 星标
- 2.9k
- 派生
- 576
- 平均合并
- 1 天 9 小时
- 30 天内合并 PR
- 78
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
NVIDIA/gpu-operator 的其他 Issue
-
feature lifecycle/frozen needs-triage
难度 2/5 1-3 小时 新手友好度 68/100
NVIDIA/gpu-operator#3074 ·
维护者通常 1 天内回复
-
bug needs-triage
难度 2/5 1-3 小时 新手友好度 75/100
NVIDIA/gpu-operator#3065 ·
维护者通常 1 天内回复
-
[Bug]: ClusterPolicy isDaemonSetReady can report Ready from a DaemonSet status of an older generation可能已有人在做 @efegokdemir 于 3 天前认领。 未关闭bug needs-triage
难度 2/5 1-3 小时 新手友好度 72/100
NVIDIA/gpu-operator#3060 · 1 条评论 ·
维护者通常 1 天内回复
-
[Bug]: GPUCluster common name label breaks DRA validator selector可能已有人在做 @ajavanma 于 25 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 88/100
NVIDIA/gpu-operator#2955 · 1 条评论 ·
维护者通常 1 天内回复
-
[Bug]: driver-validation hides why a pre-installed driver failed and loops without a reason可能已有人在做 @fjvbn2003 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 25/100
NVIDIA/gpu-operator#3085 ·
维护者通常 1 天内回复
查看 NVIDIA/gpu-operator 的全部 Issue
相似的 Issue
-
kind/bug
难度 2/5 1-3 小时 新手友好度 74/100
kubernetes-sigs/kueue#17385 ·
维护者通常 1 天内回复
-
Tablet Pods keep only one of several topology spread constraints that share a label selector可能已有人在做 @RaphaelFakhri 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
planetscale/vitess-operator#858 ·
维护者通常 2 天内回复
-
Realtime: ASR EOU language tags leak into the LLM conversation (unintended reply-language switching)可能已有人在做 @nexxtmobile 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
content:edit documentation effort:high
难度 1/5 1-3 小时 新手友好度 67/100
cloudflare/cloudflare-docs#34428 ·
维护者通常 1 天内回复
-
generate: duplicate-skill warning ignores lint.allow_overrides when a local skill shadows a builtin未关闭
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复