Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Verify the triggering commit before running other CI jobs

未关闭
#2,990 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@Coelho-Gustavo 已经在做这个了。

开始于 2026年10月1日。

  • #2992 来自 @Coelho-Gustavo —— 未关闭

评估

难度
3/5
预计耗时
1-2 天
新手友好度
78/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
github-actions
领域
ci-cd, security

调研方向

Start with .github/workflows/ci.yaml to map its jobs and existing needs, then add the reusable .github/workflows/commit-verification.yaml workflow using github.sha and GitHub signature-verification metadata. Update every other CI job to depend on commit-verification while preserving existing dependencies. Done means an unverified or unavailable commit fails with its SHA and reason, and dependent jobs run only after successful verification.

由索引模型根据 Issue 内容生成。

描述

good-first-issue

PRs can pass DCO while containing unsigned or unverified commits. DCO sign-off does not verify commit signatures.
Add a reusable workflow, .github/workflows/commit-verification.yaml, with:

on:
  workflow_call: {}

permissions:
  contents: read

The workflow should check GitHub’s signature-verification metadata for the triggering commit (github.sha) and fail if it is not verified. Report the commit SHA and verification reason, and fail if verification metadata cannot be retrieved.
Call it from .github/workflows/ci.yaml:

jobs:
  commit-verification:
    permissions:
      contents: read
    uses: ./.github/workflows/commit-verification.yaml

Make all other CI jobs depend on commit-verification through needs, preserving existing dependencies, so verification runs first and subsequent jobs run only after it succeeds.

主要语言
Go
星标
2.9k
派生
569
平均合并
1 天 10 小时
30 天内合并 PR
78

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

NVIDIA/gpu-operator 的其他 Issue

查看 NVIDIA/gpu-operator 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。