Git Repo Window ColorsColor your VSCode Windows based on which git repo you are working in. What it doesThis extension allow you to give your VSCode window a custom color based on the repository name of the git repository opened as your worksapce. It does this by immediately writing color settings in This plugin works best with these two settings also set:
If you are like me and have multiple vscode windows opened all the time, working on different repositories, you know it can be hard to differentiate the windows visually. By assigning custom colors to the title and activity bars, this plugin aims to alleviate this problem. This also helps when viewing the thumbnail previews displayed by most docks (Windows Taskbar, Ubuntu Dock, etc...) UsageLET IT BE KNOWN: Any custom color settings managed by this plugin that you may have defined previously in a workspace .vscode/settings.json will be overwritten by this extension. To configure this extension, open the Settings UI and look for "Git Repo Window Colors" extension settings. Repo Configuration SettingAt a minimum you need to add entries to the 'Repo Configuration List'. This setting is a configurable list of string entries. Each string has this format schema:
Where:
The color value can be any color string code recognized by javascript When editing the settings, the VSCode window will respond immediately to your edits. Any errors (broken json, unknown color codes, etc...) are reported via VSCode notifiaction messages. Any entry with an error is ignored. If your workspace folder is not a git repo, then no coloring will happen. Branch Configuration SettingThe Repo Configuration describe above can do basic branch indications like "I'm working on the default branch" (one color) or "I'm working on a non-default branch" (another color). The Branch Configuration section takes this to the NEXT LEVEL. Using this section is completely optional, but you may find it hard to resist the power it offers. Using this setting you can assign custom colors to specific branch names or branch patterns. Say you are using a bug tracker like Jira where you have FEATURE and BUG type issues. Your flow mandates that you create branch names like Each entry in this section is a simple Setting SyncIf you use Settings Sync then these color configuraiton will apply everywhere you use vscode. It's pretty coolr to change a color setting in one instance and see it updated in other instance (on the next sync cycle) NotesThis extension works best when you have .vscode/settings.jon in your .gitignore file (either locally or globally). It will work without this, but you may end up committing your custom colors to your repo which might be problematic to other people working in your repo that do not have this SUPER COOL extension installed. I highly recommend you just tell them to install it. Workspaces containing multiple root folders may not behave predictably. The current behavior for multi-folder workspaces is that the workspace color settings will be set by the first window opened, and can be saved in the workspace's When opening new vscode windows, you might see the relevant theme colors change as they are updated to the new workspace. This is normal. CreditsThis projects was inspired by and forked from https://github.com/stuartcrobinson/unique-window-colors. More than 90% of the code has been rewritten. |