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

test(source-control): put the eval gh fixture on PATH without relying on zsh's .zshenv

Abierto
  • ¿Algo no está bien?
#7,176 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
bash, github-actions, shell, zsh
Área
devtools, testing

Línea de trabajo

Start with plugins/source-control/evals/fixtures/gh-forge/install.sh and the case.yaml environment limits described in the issue; review the findings from #7164 and the runner capability options. The change depends on an upstream runner capability request and a kept-trace run on a bash-SHELL host. Done means ready cases reach gh pr ready through the stand-in and install.sh no longer writes ~/.zshenv.

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

Descripción

needs-human needs-triage

Context

Follow-up to #7164 (#6997). The owner accepted zsh-only coverage for the offline gh fixture so that PR could merge; this issue tracks the shell-independent fix.

Problem

plugins/source-control/evals/fixtures/gh-forge/install.sh puts the stand-in gh on PATH only by appending an export to the run's ~/.zshenv. On a host whose SHELL is bash (a default CI runner, for example), the stand-in is never on PATH: the run falls through to the real gh, which has no login inside the run and no network under the sandbox, so the ready cases stop at the PR lookup again.

Evidence from #7164 (Claude Code 2.1.296 probes):

  • A case cannot set PATH: case.yaml env keys are limited to EVAL_*.
  • The scaffold's HOME is the run's temporary home, and the eval run does not source ~/.zshrc, ~/.bashrc or ~/.profile: functions and variables defined there were missing from the run's Bash.
  • Only ~/.zshenv took effect, because zsh reads it on every zsh -c. That is undocumented runner behavior.
  • No run was made on a bash-SHELL host; the fall-through there is inferred from the above.

Ask

The clean fix needs a capability in claude plugin eval itself, for example:

  1. a case-level PATH prefix (a case.yaml key naming a directory under the scaffolded workspace to prepend), or
  2. a scaffold-written env file the runner applies to the run's shell.

This repository cannot add either; record the request upstream through the owner's normal channel, then switch gh-forge/install.sh to the new mechanism and drop the .zshenv append. An operator-level dispatcher gh on PATH (option 3 in #7164) works on any shell but adds a convention to every invocation; it stays the fallback if upstream declines.

Acceptance

  • The pull-request ready cases reach gh pr ready through the stand-in on a bash-SHELL host, shown by a kept-trace run.
  • install.sh no longer writes ~/.zshenv.

Related: #6997, #7164

Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
7 h 42 min
PR fusionados (30 d)
923

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 melodic-software/claude-code-plugins

Todos los issues de melodic-software/claude-code-plugins

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.