Improvements to mappings and automate manual steps about vscode-codicons HOT 5 OPEN

Priorities:

• 1️⃣ Automate build and publish content of dist to Releases
  • Version number increment or timestamp
  • Summary of commits/PRs
  • 1️⃣ Automatic PR to microsoft/vscode with codicons.ttf

stretch goal: automate codicons.ts file generation in vscode repo

• 2️⃣ Improve mapping.json

  • Group icon aliases
  • Automate (hex) numbering

• 3️⃣ Automate updating of relevant microsoft/vscode-docs pages

• 4️⃣ Github Pages site to browse icons

from vscode-codicons.

• stretch goal: automate codicons.ts file generation in vscode repo

from vscode-codicons.

I've completed the following:

• dist/ is now in .gitignore
• use gh-pages.yml to publish the website (putting back dist/)
• codicons.ttf is uploaded as a build artefact for each build job
• a draft Release gets made automatically when pushing a new annotated tag, including all commit messages since the previous release.
  • codicon.ttf artefact is included in Releases

On the vscode side I've split up the list of icons into a library and a derived list. The library is a separate file that the codicons build generates with a new script: scripts/convert-to-ts.js. I've made sure any mixed-in aliases got moved to the derived list. vscode merges these lists at runtime, so everything works as normal, but without the conflicts.

The only missing step is to automatically create a PR to microsoft/vscode repo when a new commit happens on main. There seems to be an authentication issue here and we probably need to flip a setting or get a token from somewhere to make it work.

The rest of the ideas above are stretch goals. Having automated PRs to VS Code is the major time saver.

@mrleemurray would love your help with this last step. :)
cc @daviddossett

from vscode-codicons.

Separate issue for the mapping improvements: #239

from vscode-codicons.

Link #232, #234, #235, #236

from vscode-codicons.