Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Add `.github/workflows` path to `require` paths

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
42/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
github-actions, javascript, typescript
Área
ci-cd

Línea de trabajo

The issue does not name a file or test. Start by locating the require-path setup used by workflow scripts and compare the existing behavior with process.env.NODE_PATH and module.paths. Done means require can search .github/workflows without changing the current project-root behavior.

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.
It took me a while to figure out how to include files in this project, because I had (incorrectly) assumed the relative path was to the .github/workflows folder and not the project root. I would assume this is a common misunderstanding, as the user is writing their script inside that folder.

Describe the solution you'd like
I certainly don't recommend changing the behavior, but simply adding the workflow's .github/workflows path in the list of paths for require to search.

Describe alternatives you've considered
Alternatively, make a way for users to add their own relative paths to the configuration or the script, which might be a better approach.

It seems of the two common ways of doing this (namely, modifying the process.env.NODE_PATH environment variable or pushing a path onto module.paths), neither is implemented. The easiest method might be to simply make use of the process.env.NODE_PATH environment variable as the core functionality does.

Additional context
N/A

Lenguaje dominante
TypeScript
Estrellas
5k
Forks
586
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

  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 actions/github-script

Todos los issues de actions/github-script

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.