Fixes #4207 - Incorrect PR Link Across Azure DevOps Projects #4210
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request resolves an issue where GitLens incorrectly links pull requests when a commit originates from a different Azure DevOps project, despite the commit tree being visible in the current project.
When a commit from a pull request (PR) in one Azure DevOps project (e.g., Project B) is reflected in another project (e.g., Project A) due to shared repositories or mirrored refs, GitLens correctly displays the commit in Project A. However, it incorrectly assumes the associated PR also exists in Project A, resulting in a broken or invalid PR link. Since PRs are scoped to their respective projects, this leads to a mismatch between the commit’s origin and the generated PR URL.
Fix includes using
pr.repository.project.namewhen fetching the repository name, rather than just the currentprojectName.Checklist
Fixes $XXX -orCloses #XXX -prefix to auto-close the issue that your PR addresses