Feature request: repo-local configuration file support

Abierto
  • ¿Algo no está bien?
#133 0 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

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

Línea de trabajo

Start by tracing cooldown configuration lookup across .github/dependabot.yml, ~/.config/gh-actions-lock/config.yml, and GH_ACTIONS_LOCK_CONFIG, then compare the proposed .github/actions-lock.yml behavior. Done means repo-local settings are auto-discovered, take the documented priority, and provide cooldown without requiring Dependabot or an environment variable.

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

Descripción

area:cli feature-request

Feature request: repo-local configuration file support

Summary

Add support for a repo-local configuration file dedicated to gh-actions-lock (e.g. .github/actions-lock.yml).

Today the only file-based setting is cooldown, and its lookup sources are limited to .github/dependabot.yml (the github-actions update entry's cooldown block) or ~/.config/gh-actions-lock/config.yml (or an arbitrary path via GH_ACTIONS_LOCK_CONFIG).

Motivation

  • Repositories using a dependency updater other than Dependabot (e.g. Renovate) cannot manage cooldown in-repo without enabling Dependabot's github-actions updater as a side effect (open-pull-requests-limit: 0 suppresses PRs but the updater still runs).
  • ~/.config/... is user-global and can't be git-managed per repository; GH_ACTIONS_LOCK_CONFIG requires setting an env var on every invocation, which is easy to forget.
  • A dedicated repo-local config file gives future repo-scoped settings a home beyond cooldown.

Proposal

Auto-discover a repo-local config file (e.g. .github/actions-lock.yml) and read it with priority equal to or above dependabot.yml. Use it as the home for repo-scoped settings, starting with cooldown.

Lenguaje dominante
Go
Estrellas
295
Forks
21
Merge medio
19 h 30 min
PR fusionados (30 d)
60

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.