SCM - fix rendering issue with incoming changes node#276055
Merged
Conversation
lszomoru
force-pushed
the
lszomoru/fascinating-dormouse
branch
from
3b68f18 to
6ae01a1
Compare
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds a conditional check to only show incoming changes in the SCM history graph when the remote history item reference is actually part of the graph being displayed.
- Changed behavior: The incoming changes node is now only added if both the configuration is enabled AND the remote reference exists in the current graph's history item references
joaomoreno
approved these changes
Nov 7, 2025
lszomoru
added a commit
that referenced
this pull request
Nov 7, 2025
SCM - fix rendering issue with incoming/outgoing changes nodes
lszomoru
added a commit
that referenced
this pull request
Nov 7, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Related #275820