Feature request: allow selected action owners to be explicitly excluded from lockfile pinning

未关闭
  • 哪里不对？
#194 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
github-actions, go
领域
cli, security

调研方向

Start by tracing how gh actions-lock resolves workflow refs, reports findings such as self-repository-action, and verifies lockfile entries; then inspect runtime enforcement and lockfile parsing. The issue names no source files or tests, so locate those entry points first. Done means exclusions are recorded with reasons in the lockfile, reported during resolution, and treated as compliant by verification and enforcement only when listed.

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

描述

feature-request

Problem

Our workflows mix public GitHub-maintained actions with internal actions published by our own organization, e.g.:

steps:
  - uses: actions/checkout@v7
  - uses: internal-action/build-image@v1

We want SHA-locked integrity for third-party/public actions (actions/*), but our internal actions are deliberately consumed via a floating major tag (@v1). They are released frequently under our own access controls and review process, and we want consumers to pick up patch releases without a lockfile change for every internal release.

Today gh actions-lock has no way to exclude specific actions or owners. Because enforcement requires every dependency of an onboarded workflow to be present in actions.lock, our only options are:

  1. Lock internal actions too and run --relock constantly (heavy churn for every internal release), or
  2. Leave the whole workflow un-onboarded, losing protection for the public actions as well.

Neither is a good fit. Option 2 in particular pushes teams to skip locking entirely.

Proposal

Support an explicit, auditable exclusion recorded in the lockfile itself (not only as a CLI flag), so the runtime can tell "intentionally unlocked" apart from "missing":

# .github/workflows/actions.lock
unlocked:
  - owner: internal-action        # or a pattern like 'my-org/*'
    reason: 'Internal actions, governed by org release process'

Suggested behavior:

  • gh actions-lock skips resolution for matching refs and reports them as an informational finding (similar to self-repository-action), never silently.
  • --verify / --verify-local treat matching refs as compliant only if they are listed under unlocked.
  • Runtime enforcement accepts listed refs unpinned and still requires everything else to be locked.
  • Optionally, restrict eligible owners (e.g. same owner/org as the repository, or an org-level policy) so this can't be used to unlock arbitrary third-party actions.
主要语言
Go
星标
253
派生
15
平均合并
19 小时 30 分钟
30 天内合并 PR
60

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

github/gh-actions-lock 的其他 Issue

查看 github/gh-actions-lock 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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