Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

source-control: read-pr.sh calls GraphQL before its REST read, so it fails in cloud sessions

Open Beginner friendly
#7,223 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
github, shell
Domain
tooling

Research direction

Read plugins/source-control/skills/pull-request/scripts/read-pr.sh around line 113, then compare the fallback behavior in babysit_gh.py and morning-brief.sh mentioned in the issue. Verify that the REST read runs before any failing GraphQL call, or that the specified GraphQL refusal triggers the REST fallback; the script should complete its pull request visibility read in cloud sessions.

Written by the indexing model from the issue text.

Description

good first issue needs-triage priority: high

Problem

plugins/source-control/skills/pull-request/scripts/read-pr.sh:113 runs gh pr view --json (GraphQL) before its REST visibility read. The cloud GitHub proxy refuses every GraphQL request with a 403 (https://code.claude.com/docs/en/cloud-environments#github-proxy, read 2026-10-11), so in a cloud session the script exits before the REST read runs.

Fix direction

Do the REST read first, or fall back to gh api repos/{owner}/{repo}/pulls/{n} when the GraphQL call returns the proxy's "GitHub GraphQL is not available from Claude Code sessions" refusal, matching the fallback babysit_gh.py and morning-brief.sh use after #7219.

Related

  • #7219 (updated the GraphQL-refusal matchers)

🤖 Generated with Claude Code

Dominant language
Shell
Stars
22
Forks
2
Avg merge
6h 42m
Merged PRs (30d)
902

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from melodic-software/claude-code-plugins

All issues in melodic-software/claude-code-plugins

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.