Allow placing `actions.lock` in `.github` folder (not in workflows)

Abierto
#262 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
42/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions, go
Área
cli, devops

Línea de trabajo

The lockfile path is resolved by the CLI extension written in Go; start from wherever workflows/actions.lock is referenced and how the lock file is located and read. Add .github/actions.lock as a fallback while keeping .github/workflows/actions.lock as the higher-priority path. Done when both locations resolve correctly and a test covers the priority order.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Background & Motivation

When pushing changes to .github/workflows, I want to automatically update and commit (create PR) actions.lock within CI using GITHUB_TOKEN. To make this possible, actions.lock needs to be supported in an alternative path outside of .github/workflows, as GITHUB_TOKEN is not allowed to write content in workflows folder.

Because standard lockfile updates (without --relock) are purely additive operations, I believe that allowing automated lockfile updates upon push (create PR) does not cause unintended modifications or regression hazards.

Proposed Changes

  • Support .github/actions.lock: Allow actions.lock to reside directly in the .github/ directory as an alternative path.
  • Resolution Priority: Continue support for .github/workflows/actions.lock. This allows user can specify the hash for the action that won't be changed by CI workflow.
Lenguaje dominante
Go
Estrellas
295
Forks
21
Merge medio
1 d 3 h
PR fusionados (30 d)
64

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/gh-actions-lock

Todos los issues de github/gh-actions-lock

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.