Add secondary overview ruler colors for staged changes #249711
Draft
+33
−6
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.
Overview
This PR adds secondary foreground colors for diff decorations in the editor overview ruler for staged changes, matching the existing functionality available for the editor gutter.
Problem
Currently, users can customize the appearance of staged changes in the editor gutter using the following color theme settings:
editorGutter.addedBackground
andeditorGutter.addedSecondaryBackground
editorGutter.modifiedBackground
andeditorGutter.modifiedSecondaryBackground
editorGutter.deletedBackground
andeditorGutter.deletedSecondaryBackground
However, there are no equivalent "secondary" colors for the overview ruler, which limits the ability to visually distinguish between regular and staged changes in the overview ruler.
Solution
Added three new color theme settings:
editorOverviewRuler.addedSecondaryForeground
editorOverviewRuler.modifiedSecondaryForeground
editorOverviewRuler.deletedSecondaryForeground
These new color settings follow the same pattern as the existing secondary gutter colors, using appropriate transparency and color derivations to maintain visual consistency.
Implementation Details
Fixes #249561.
Warning
Firewall rules blocked me from connecting to one or more addresses
I tried to connect to the following addresses, but was blocked by firewall rules:
electronjs.org
node-gyp
(dns block)playwright-akamai.azureedge.net
/usr/local/bin/node /home/REDACTED/work/vscode/vscode/node_modules/playwright-core/lib/server/registry/oopDownloadBrowserMain.js
(dns block)playwright-verizon.azureedge.net
/usr/local/bin/node /home/REDACTED/work/vscode/vscode/node_modules/playwright-core/lib/server/registry/oopDownloadBrowserMain.js
(dns block)playwright.azureedge.net
/usr/local/bin/node /home/REDACTED/work/vscode/vscode/node_modules/playwright-core/lib/server/registry/oopDownloadBrowserMain.js
(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.