Issues workflow fails on every opened issue because issues.cjs is called without its arguments

Cerrado
  • ¿Algo no está bien?
#1,786 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

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
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions, node.js, typescript
Área
ci-cd, tooling

Línea de trabajo

Read .github/workflows/issues.yaml and .github/scripts/issues.cjs, then compare the script’s assumptions with .agents/skills/opening-issues/SKILL.md and the current issue templates. Verify the workflow behavior by opening and reopening a test issue; done means no failed Issues run and no unwanted title change, or that the obsolete workflow and script are removed.

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

Descripción

Area: Infrastructure Bug Difficulty: Low Good First Issue Priority: Low

The "Issues" workflow fails on every issue that is opened or reopened. The workflow calls require('./.github/scripts/issues.cjs')() with no arguments. The module's default export forwards its args parameter to addPriorityAndDifficulty({ context, github }), so the destructure throws TypeError: Cannot destructure property 'context' of 'undefined' before any API call. All 195 runs GitHub still retains failed, from 2025-09-16 to today. The call has had no arguments since the script was moved out of the workflow in Feb 2024. Every new issue therefore adds a red run to the Actions tab and sends a failure notification. A plain fix would also do the wrong thing. The issue templates no longer contain the Priority and Estimated Difficulty sections the script parses, so it would call addLabels with an empty list. .agents/skills/opening-issues/SKILL.md says titles carry no [Bug]:-style prefix, yet the script would add one to every title, and on reopened it would add a second ([Bug]: [Bug]: …).

Where

.github/workflows/issues.yaml:16-20:

- name: Run Script
  uses: actions/github-script@v9
  with:
    script: |
      require('./.github/scripts/issues.cjs')()

.github/scripts/issues.cjs:4 and :51-54:

function addPriorityAndDifficulty({ context, github }) {
// ...
module.exports = (args) => {
  addPriorityAndDifficulty(args);
  addLabelToTitle(args);
};

Reproduce

  1. Open any issue on the repository.
  2. Open the triggered "Issues" run (gh run list --workflow=Issues --limit 1) and read its log.

Actual: ##[error]Unhandled error: TypeError: Cannot destructure property 'context' of 'undefined' as it is undefined. (for example, run 37676175978).
Expected: either the workflow does something useful and succeeds, or it does not exist.

Tests

No unit or Playwright test can run a GitHub workflow. Verify the fix by opening and then reopening a test issue, and confirming that no "Issues" run fails and that the title is unchanged.

Suggested fix

Delete .github/workflows/issues.yaml and .github/scripts/issues.cjs. The templates no longer feed the label step, and the title step contradicts the documented title convention. If automatic labelling is still wanted, reimplement it against the current templates. Pass { context, github } from the workflow, await both API calls, and skip addLabels when there is nothing to add.

Lenguaje dominante
TypeScript
Estrellas
119
Forks
19
Merge medio
4 d 12 h
PR fusionados (30 d)
39

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 DouglasNeuroInformatics/OpenDataCapture

Todos los issues de DouglasNeuroInformatics/OpenDataCapture

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.