Migration occurs when colors are in user settings but not in workspace.

• OS: Mac 10.14.5
• VS Code: 1.37.1
• Peacock Version: 3.1.1

Peacock is creating new workspace settings when surpriseMeOnStartup is false.

$ rg peacock ~/Library/Application\ Support/Code/User/settings.json
95:    "peacock.surpriseMeOnStartup": false,
96:    "peacock.affectStatusBar": false,
97:    "peacock.affectActivityBar": false,
98:    "peacock.affectAccentBorders": false,
99:    "peacock.affectTabActiveBorder": true,
100:    "peacock.favoriteColors": [
$ ls -a
./  ../
$ code .
$ ls -a
./  ../  .vscode/
$ bat --style=header,numbers .vscode/*
     File: .vscode/settings.json
   1 {
   2     "peacock.color": "#777",
   3     "workbench.colorCustomizations": {
   4         "titleBar.activeBackground": "#777777",
   5         "titleBar.inactiveBackground": "#77777799",
   6         "titleBar.activeForeground": "#e7e7e7",
   7         "titleBar.inactiveForeground": "#e7e7e799",
   8         "tab.activeBorder": "#909090"
   9     }
  10 }

With Peacock disabled:

$ ls -a
./  ../
$ code .
$ ls -a
./  ../

[johnpapa]

thanks for verifying.

[kbd]

At some point I created these workspace settings:

Just to clarify, I mistyped “workspace” when I meant “workbench”.

Fix is being testing in CI and pending in v3.1.4

Just confirmed that on 3.1.4 no workspace settings.json is written in a fresh directory. Thanks for fix!