work-items: github adapter takes GraphQL paths on gh 2.94+ even in cloud sessions, whose proxy refuses GraphQL
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
Línea de trabajo
Start with plugins/work-items/tools/work-item-tracker/lib/gh-version.sh and the read and create paths in adapters/github/common.sh and adapters/github/create-item.sh. Trace how the native gh surface is selected and how REST fallback currently works, then check the related cloud session behavior described in the issue. Done means reads and creates use REST when GraphQL is unavailable, with sub-issue and dependency operations reporting that they are unavailable in that environment.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
The work-items GitHub adapter picks its read and create paths by gh version alone. On gh 2.94 or newer it reads items through gh issue view --json and creates them with native gh issue create, and both go through GraphQL. The live docs say the GitHub proxy in Claude Code cloud sessions refuses every GraphQL request, so in a cloud session with a new enough gh the adapter's read and create paths fail. The REST fallback exists, but only for older gh.
Affected area / component
plugins/work-items/tools/work-item-tracker/adapters/github/ (common.sh, create-item.sh) and plugins/work-items/tools/work-item-tracker/lib/gh-version.sh
Steps to reproduce
- In a Claude Code cloud session, install
gh2.94 or newer. - Read or create an item through the work-item-tracker seam with the github adapter.
(Repro is from the code path and the docs; not run in a cloud session.)
Expected behavior
In a session whose GitHub proxy refuses GraphQL, the adapter uses its REST paths whatever the gh version.
Actual behavior
lib/gh-version.sh:22-30(wit_gh_has_native_surface): returns 0 whenghis present and at least 2.94. It checks nothing about the environment.adapters/github/common.sh:338-347(wit_emit_item): with the native surface, reads throughgh issue view --json; REST is used only otherwise.adapters/github/create-item.sh:61setsnative=1from the same check, and:87then runsgh issue create. The REST branch at:116-118already notes that "gh issue createresolves through GraphQL, which sandboxed sessions refuse with HTTP 403".- Live docs, https://code.claude.com/docs/en/cloud-environments#github-proxy (read 2026-10-12): the proxy "rejects requests to GitHub's GraphQL endpoint with a 403", and "
ghsubcommands that use GraphQL, such asgh prandgh issue, get the same 403", regardless of the credentials supplied.
Suggested fix
Route to REST when the session is behind the proxy: detect a cloud session, or treat a GraphQL 403 whose message starts with "GitHub GraphQL is not available from Claude Code sessions" as a signal to fall back. Sub-issue and dependency edges have no REST form, so they need an explicit "unavailable here" error rather than a failed call.
Related: #3169 (cloud sessions ship an older gh, so today the version gate keeps them on REST by accident), #7240, #7223.
Environment
work-items on main as of 2026-10-12; Claude Code cloud sessions.
Found during the upstream-pointer sweep (PRs #7061-#7274).
- Lenguaje dominante
- Shell
- Estrellas
- 22
- Forks
- 2
- Merge medio
- 8 h 25 min
- PR fusionados (30 d)
- 944
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de melodic-software/claude-code-plugins
-
good first issue priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
melodic-software/claude-code-plugins#7530 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
needs-human priority: medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
melodic-software/claude-code-plugins#7455 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
priority: medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
melodic-software/claude-code-plugins#7351 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
agent-ready priority: high work-class: scoped
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
melodic-software/claude-code-plugins#7312 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
priority: medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
melodic-software/claude-code-plugins#7288 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de melodic-software/claude-code-plugins
Issues similares
-
Standalone Unix updater reports success when curl fails (`curl | sh` masks the exit status); Windows path is unaffectedPosiblemente ocupada @akhil9tiet la tomó hoy. Abiertobug CLI windows-os
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
openai/codex#54465 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
interledger/rhyza#352 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
non7top/dotfiles-personal#41 ·
Los mantenedores suelen responder en 1 día
-
Build: the CUDA backend fails without cuDNN instead of skipping the cuDNN shim (as the cuDF shim does)Posiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
beehive-lab/TornadoVM#1248 ·
Los mantenedores suelen responder en 1 día
-
Dev
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
ankidroid/Anki-Android#22555 ·
Los mantenedores suelen responder en 1 día