Skip to content

Git Blame - git commits always opens in GitHub as the upstream repo #250794

@yCodeTech

Description

@yCodeTech

Type: Bug

When using Git Blame's "Open on GitHub" button, the commit opens on the upstream repo if it's set as one of the remotes, even when the commit is not apart of that repo and is committed on the origin repo. A warning is also displayed on GitHub:

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

The commits should be opening in the origin repo not the upstream. If I remove the upstream remote, then opening commits work as aspected.

A somewhat related issue is #239878; the Git Blame extension as mentioned in the issue also opens commits as aspected in the origin repo with the default settings.

VS Code version: Code 1.100.3 (258e40f, 2025-06-02T13:30:54.273Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info
Item Value
CPUs AMD Ryzen 7 3700X 8-Core Processor (16 x 3593)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) undefined
Memory (System) 15.91GB (1.96GB free)
Process Argv --crash-reporter-id 7a4b0ae5-426b-444e-afa1-21d384c72265
Screen Reader no
VM 0%

Metadata

Metadata

Assignees

Labels

gitGIT issuesinsiders-releasedPatch has been released in VS Code Insiders

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions