Request: let trusted actions keep floating tags in onboarded workflows

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start by reading the repository’s policy and lockfile enforcement entry points; the issue does not name specific files or tests. Identify how onboarded workflows currently validate action references, then assess what administrator policy would need to change to allow selected actions to use floating tags such as @v1. Done means the proposed policy is defined and specific trusted actions can remain floating while other dependencies stay locked.

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

描述

We'd like to adopt lockfiles and turn on require lockfile across our enterprise's organizations. Right now, once a workflow is onboarded, every action dependency has to be locked, including the actions our own orgs owns. We want some internal actions to continue supporting a floating tag @v1 so fixes and security patches reach every caller right away.

Proposal - let enterprise administrators define a policy to allow specific github actions to use a floating tag.

主要语言
Go
星标
317
派生
24
平均合并
1 天 8 小时
30 天内合并 PR
50

环境准备

  • 没有 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 摘要。