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

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

Aperta
  • Qualcosa non va?
#7,176 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
bash, github-actions, shell, zsh
Ambito
devtools, testing

Direzione di ricerca

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.

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

Descrizione

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

Lingua principale
Shell
Stelle
22
Fork
2
Merge medio
7h 42m
PR unite (30g)
923

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.