Repository navigation
compliance-vscode-theme - #896
Merged
Merged
Conversation
VeryComplexAndLongName
enabled auto-merge (squash)
October 11, 2026 14:54
VeryComplexAndLongName
force-pushed
the
compliance-vscode-theme
branch
from
October 11, 2026 14:59
13ea30f to
dde3da6
Compare
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Make the Compliance VS Code webview mount the shared Metro root and
useEditorDarkThemeadapter, matching the Pipeline and Harness Settings webviews. It now follows light, dark, high-contrast and high-contrast-light changes while open; standalone theme behavior is unchanged.Verification
Fixes the post-merge report that Compliance alone did not follow VS Code themes.