Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] `--from-pr` docs still describe GitHub-only PR URL support [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52604•Fetched 2026-04-24 06:02:41
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeek
Timeline (top)
labeled ×4
RAW_BUFFERClick to expand / collapse

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/cli-reference

Section/Topic

The --from-pr flag entry in the CLI flags table, plus the resume-from-PR guidance in Common workflows.

Current Documentation

The docs currently say:

--from-pr — Resume sessions linked to a specific GitHub PR. Accepts a PR number or URL. Sessions are automatically linked when created via gh pr create.

And the workflow docs say:

When you create a PR using gh pr create, the session is automatically linked to that PR. You can resume it later with claude --from-pr <number>.

claude --from-pr 123 resumes sessions linked to a specific pull request

What's Wrong or Missing?

Changelog v2.1.119 says --from-pr now accepts GitLab merge-request URLs, Bitbucket pull-request URLs, and GitHub Enterprise PR URLs.

The current docs still frame --from-pr as GitHub-only and only show a numeric pull-request example. That leaves the CLI reference and workflow guidance outdated for users working with GitLab, Bitbucket, or GitHub Enterprise pull-request URLs.

Suggested Improvement

Update the --from-pr flag documentation to list the supported URL types explicitly instead of saying only "GitHub PR".

Suggested changes:

  • In cli-reference, describe --from-pr as accepting a PR/MR number when available plus GitHub, GitHub Enterprise, GitLab merge-request, and Bitbucket pull-request URLs.
  • In common-workflows, expand the resume guidance beyond claude --from-pr 123 and add URL examples for at least one non-GitHub host.
  • Clarify whether automatic linking via gh pr create is GitHub-specific while manual --from-pr <url> supports additional providers.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageLine(s)Context
https://code.claude.com/docs/en/cli-reference71--from-pr is described as a specific GitHub PR and does not mention GitLab, Bitbucket, or GitHub Enterprise URLs
https://code.claude.com/docs/en/common-workflows360, 555Resume guidance only shows gh pr create linking and claude --from-pr 123

Total scope: 2 pages affected

Source: Changelog v2.1.119

Changelog entry: --from-pr now accepts GitLab merge-request, Bitbucket pull-request, and GitHub Enterprise PR URLs

extent analysis

TL;DR

Update the --from-pr flag documentation to include support for GitLab, Bitbucket, and GitHub Enterprise URLs.

Guidance

  • Review the current documentation for --from-pr in the CLI reference and common workflows sections to identify outdated information.
  • Update the documentation to explicitly list the supported URL types, including GitHub, GitHub Enterprise, GitLab merge-request, and Bitbucket pull-request URLs.
  • Add examples of using --from-pr with non-GitHub URLs in the common workflows section.
  • Clarify whether automatic linking via gh pr create is GitHub-specific and if manual --from-pr <url> supports additional providers.

Example

No code snippet is necessary for this issue, as it is related to documentation updates.

Notes

The suggested changes should be applied to the affected pages, which are the CLI reference and common workflows sections.

Recommendation

Apply the suggested documentation updates to reflect the changes in --from-pr support, as mentioned in Changelog v2.1.119. This will improve the accuracy and helpfulness of the documentation for users working with different Git providers.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#memory optimization#batch processing#GPU compatibility#latency issue#model loading

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [DOCS] `--from-pr` docs still describe GitHub-only PR URL support [1 participants]