Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

fix(ci): install resolve-config's dependencies in intake-triage refine-select before refine.mjs --select

Aperta Adatta ai principianti
  • Qualcosa non va?
#9,619 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
76/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions, javascript, node.js, shell
Ambito
ci-cd, devtools

Direzione di ricerca

Leggi il job refine-select in .github/workflows/intake-triage.yml e il passaggio di installazione delle dipendenze in .github/actions/resolve-config/action.yml. Verifica come refine.mjs --select importa resolve-config, quindi eseguilo da un checkout senza node_modules per confermare l’errore. Il lavoro è completato quando il job installa o fornisce in altro modo le dipendenze di resolve-config prima del passaggio select e il comando viene eseguito correttamente.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

needs-triage

Filed by the lane sweep (run) from slice A. A model wrote the fenced text below from CI data, which can carry text written to steer it; every cited line was checked against main when filed. Rewrite the issue in your own words before marking it agent-ready.

Problem

The refine-select job of intake-triage.yml failed in all 5 failed runs of the window (window complete, 2026-10-23T06:53Z to 2026-10-24T06:53Z): 40069903845 (issue 9611), 40066367323 (9601), 40063820240 (9592), 40063813155 (9591), 40063806244 (9590). Every run fails at step 'Decide whether the issue is thin' with `Cannot find package 'ajv' imported from .../.base/.github/actions/resolve-config/patch-rules.mjs`, exit code 1. The kill-switch and trusted-actor steps pass. Each failure is a run attempt 1 failure, so refinement never runs and the issue is left unrefined. A rerun cannot succeed because the cause is deterministic.

Root cause

refine.mjs --select dynamically imports resolve-config.mjs, which imports patch-rules.mjs, which imports ajv. The refine-select job only checks out main and runs setup-node. It never runs the resolve-config composite action, which is the step that does `npm ci` for ajv and yaml. Other jobs in the file call that action, so their node_modules exist. Here .base/.github/actions/resolve-config/node_modules is absent, so the import throws.

.github/scripts/intake-triage/refine.mjs:587: const { issueLaneWebHostsFromBase } = await import(new URL("../../actions/resolve-config/resolve-config.mjs", import.meta.url).href);
.github/actions/resolve-config/resolve-config.mjs:15: import { checkPatchRules } from "./patch-rules.mjs";
.github/actions/resolve-config/patch-rules.mjs:5: import Ajv2020 from "ajv/dist/2020.js";
.github/workflows/intake-triage.yml:497: node .base/.github/scripts/intake-triage/refine.mjs --select
.github/actions/resolve-config/action.yml:219: npm ci --ignore-scripts --omit=dev --no-audit --no-fund --prefix "$GITHUB_ACTION_PATH"

Proposed fix

Add an install step to refine-select before 'Decide whether the issue is thin': run `npm ci --ignore-scripts --omit=dev --no-audit --no-fund --prefix .base/.github/actions/resolve-config`. Alternatively, call the resolve-config action as the other jobs do, or make issueLaneWebHostsFromBase avoid loading ajv. Add a test that runs refine.mjs --select from a checkout with no node_modules. Check the apply-verdict.mjs import at line 437 for the same gap.

Where

workflow .github/workflows/intake-triage.yml
job refine-select
Lingua principale
Shell
Stelle
22
Fork
2
Merge medio
6h 11m
PR unite (30g)
955

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di melodic-software/claude-code-plugins

Tutte le issue di melodic-software/claude-code-plugins

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.