claude-code - 💡(How to fix) Fix [FEATURE] Option to hide or configure base branch for diff stats in branch status bar [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#56169Fetched 2026-05-05 05:56:24
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

When working in repos where PRs target a branch other than master (e.g., develop), the branch status bar always compares against master, showing inflated and misleading diff stats (e.g., +24k lines). There is no way to hide or reconfigure this comparison.

Proposed Solution

Add a setting in settings.json to configure the base branch used for diff stats in the status bar, or add an option to hide the stats card entirely. Example:

{ "gitStatusBaseBranch": "develop" }

This would allow teams with non-master trunk workflows to see accurate diff stats, or opt out of the display altogether.

Alternative Solutions

No response

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

No response

Additional Context

No response

extent analysis

TL;DR

To fix the issue of misleading diff stats, consider adding a setting to configure the base branch used for diff stats in the status bar.

Guidance

  • Identify the current branch comparison logic and assess the feasibility of introducing a configurable base branch setting.
  • Evaluate the potential impact of adding a new setting, such as "gitStatusBaseBranch", on the existing codebase and user experience.
  • Investigate whether hiding the stats card entirely could be a viable temporary workaround for teams with non-master trunk workflows.
  • Consider the potential benefits and drawbacks of allowing users to opt out of the display altogether.

Example

{
  "gitStatusBaseBranch": "develop"
}

This example illustrates a possible implementation of the proposed setting.

Notes

The solution relies on the assumption that the diff stats calculation can be easily modified to use a configurable base branch. Further investigation is needed to determine the technical feasibility of this approach.

Recommendation

Apply workaround: Introduce a configurable base branch setting, such as "gitStatusBaseBranch", to allow teams to specify the branch used for diff stats in the status bar. This would provide a more accurate representation of changes and address the issue at hand.

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

claude-code - 💡(How to fix) Fix [FEATURE] Option to hide or configure base branch for diff stats in branch status bar [1 participants]