Autoupdating pinned `gh-actions-lock`

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
github-actions, go
领域
devtools

调研方向

The issue discusses pinning the gh-actions-lock extension and mentions .pre-commit-config.yaml, CI, and Dependabot, but does not identify a code entry point or define a chosen solution. Start by reviewing the proposed pre-commit hook idea and the linked discussion in cli/cli#6118; done would require agreeing on an approach and specifying how the pinned version is maintained automatically.

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

描述

Any ideas if there's a way to keep gh-actions-lock extension pinned, but automated automatically?

Currently I guess I will just pin it in CI using gh extension install github/gh-actions-lock --pin v0.4.1 and will update it once I get notification locally when using gh. But gh sends notifications only when I use gh actions-lock, which I assume won't happen very often - main work on the actions.lock will be done by dependabot and command will be executed manually only when new use of some action will be introduced.

Also noticed that this repo itself had outdated pin, submitting a fix - https://github.com/github/gh-actions-lock/pull/265

Extensions currently don't have any manifests or lock files, so there's no general solution - https://github.com/cli/cli/issues/6118

Below is sort of an idea of a hack I came up with in the mentioned issue. Not ideal, since it may mean a fake .pre-commit-config.yaml just for this, but it is a solution (e.g. to use yq to read the pinned version in CI / locally during gh extension install + dependabot support).

12. Kind of a hack, but in theory if gh-action-lock had pre-commit hook, then it would be possible to use it as a manifest both locally and CI (even if pre-commit itself won't be used) and dependabot will help maintain it.

主要语言
Go
星标
295
派生
21
平均合并
1 天 3 小时
30 天内合并 PR
64

环境准备

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