claude-code - 💡(How to fix) Fix [DOCS] `claude_code.pull_request.count` docs omit MCP-tool and merge-request coverage [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#56495Fetched 2026-05-06 06:26:32
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/monitoring-usage

Section/Topic

Metrics table and Pull request counter subsection

Current Documentation

The docs currently say:

| claude_code.pull_request.count | Number of pull requests created | count |

Pull request counter

Incremented when creating pull requests via Claude Code.

What's Wrong or Missing?

This is outdated as of v2.1.129.

The v2.1.129 changelog says:

The claude_code.pull_request.count OTel metric now counts PRs/MRs created via MCP tools, not just shell commands

But the monitoring docs still describe this metric only as pull requests created via Claude Code. That misses two behavior details that now affect interpretation of exported telemetry:

A. Merge requests are included

The current wording says only "pull requests," but the metric now also counts merge requests.

B. MCP-tool creation paths are included

The current wording does not explain that the counter increments when PRs/MRs are created through MCP tools, not only through shell-command-based flows.

Users reading the current page can undercount or misclassify development activity when they interpret this metric in dashboards or alerts.

Suggested Improvement

Update the metric description and detail text to reflect the v2.1.129 behavior explicitly.

Before:

Number of pull requests created

Incremented when creating pull requests via Claude Code.

After:

Number of pull requests and merge requests created

Incremented when Claude Code creates a pull request or merge request, including creations performed through MCP tools.

If the metric name must stay claude_code.pull_request.count for compatibility, add a short note that the historical name still covers merge requests.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageLine(s)Context
https://code.claude.com/docs/en/monitoring-usage393, 422-429Metric description and pull-request counter details

Total scope: 1 page affected

Cross-reference:

PageContext
https://code.claude.com/docs/en/changelogv2.1.129 release note says the metric now counts PRs/MRs created via MCP tools

extent analysis

TL;DR

Update the claude_code.pull_request.count metric description in the monitoring documentation to reflect the inclusion of merge requests and creations via MCP tools.

Guidance

  • Review the current documentation at https://code.claude.com/docs/en/monitoring-usage and identify the sections that need updates, specifically the Metrics table and Pull request counter subsection.
  • Update the metric description to explicitly mention the inclusion of merge requests, as suggested: "Number of pull requests and merge requests created".
  • Add a note to clarify that the metric increments when creations are performed through MCP tools, not just Claude Code.
  • Verify the changes by reviewing the affected pages, including https://code.claude.com/docs/en/monitoring-usage, to ensure the updates are accurate and consistent.

Example

The updated metric description could look like this:

Number of pull requests and merge requests created Incremented when Claude Code creates a pull request or merge request, including creations performed through MCP tools.

Notes

The update should be applied to the specific lines mentioned in the affected pages, namely lines 393, 422-429 of https://code.claude.com/docs/en/monitoring-usage.

Recommendation

Apply the suggested improvement to update the metric description and detail text to reflect the v2.1.129 behavior, as it provides a clear and accurate representation of the metric's functionality.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING