Support retrieving specific repository files before executing script
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- github, github-actions, javascript, typescript
Línea de trabajo
Start by reading the action's existing input handling and script execution flow. Determine how a files input could retrieve selected repository files through the GitHub API before the main script runs, and define completion as those files being available for require() without a full checkout.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Is your feature request related to a problem? Please describe.
- Writing javascript in YAML is less than ideal. Most editors won't fully support syntax highlighting, linting, etc.
- Using the checkout action first, a user can require() a local script and run it, but performing a full checkout first for large repositories for workflows that only need to run a single script is less than optimal.
Describe the solution you'd like
- Add an additional input such as
fileswhich can be retrieved via the github API if not present, before the main script is run.
Describe alternatives you've considered
- Checking out the entire repository, then using require() and run.
- Using other 3rd party actions to load one or more repository files, then require() and run.
- Role our own to do the same thing
- Requesting actions/checkout add a
filesinput to reduce retrieved content and use that here.
Additional context
I find writing actions and workflows, even using act, to be a painful experience in general. Any additional features of an action that ease the pain somewhat are greatly appreciated. Using multiple actions to simulate something that an action could do on its own works, but it's less than ideal.
- Lenguaje dominante
- TypeScript
- Estrellas
- 5k
- Forks
- 586
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de actions/github-script
-
Dificultad 3/5 1-2 días Aptitud para principiantes 48/100
actions/github-script#728 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 52/100
actions/github-script#727 · 1 reacción ·
-
{ Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 10/100
actions/github-script#724 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
actions/github-script#723 · 1 comentario ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
actions/github-script#714 · 1 comentario · 4 reacciones ·
Todos los issues de actions/github-script
Issues similares
-
blocklist removal
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
MetaMask/eth-phishing-detect#296544 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
pastelsky/bundlephobia#1122 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
category/development priority/P2 scope/file-operations scope/testing type/enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Enatega Customer and Rider app: Add-ons price is not visible to customer after order is placed. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100