VSCode Theme based on the colour scheme of my portfolio
Go to file
2020-04-27 21:27:28 +09:00
.vscode Generate light theme 2020-03-24 15:30:23 +09:00
src Add space between groups 2020-04-27 21:27:28 +09:00
themes Use HSL luminance for out of theme colors 2020-04-27 09:05:46 +05:30
.gitignore Introduce theme generation to enforce use of Primer Colors 2020-04-23 21:34:44 +05:30
.vscodeignore Generate light theme 2020-03-24 15:30:23 +09:00
CHANGELOG.md Update CHANGELOG.md 2020-04-27 16:54:54 +09:00
icon.png Add icon 2020-04-03 22:41:27 +09:00
LICENSE Initial commit 2020-03-24 14:07:31 +09:00
package-lock.json Use HSL luminance for out of theme colors 2020-04-27 09:05:46 +05:30
package.json Merge pull request #4 from paramaggarwal/master 2020-04-27 20:35:27 +09:00
README.md Update README.md 2020-04-27 08:19:01 +05:30

GitHub VS Code theme

GitHub VS Code theme

Install

  1. Go to VS Marketplace
  2. Click on the "Install" button

Override this theme

To quickly test something, you can also override this (or any other) theme in your personal config file. Please follow the guide in the color theme documentation.

Contribute

  1. Clone and open this repo in VS Code
  2. Press F5 to open a new window with your extension loaded
  3. Open Code > Preferences > Color Theme [⌘k ⌘t] and pick the "GitHub Light" theme
  4. Run npm install to install the Primer CSS color reference and run npm start to run the converter.
  5. Make changes to the /src/theme.js file.
    • UI: For all changes to the "outer UI", like (status bar, file navigation etc.), take a look at the Theme Color reference.
    • Syntax: For changes to the "code highlighting", examine the syntax scopes by invoking the Developer: Inspect Editor Tokens and Scopes command from the Command Palette (Ctrl+Shift+P or Cmd+Shift+P on Mac) in the Extension Development Host window.
  6. Commit your changes and open a PR.

Note:

  • If possible use colors from Primer's color system.
  • Changes to the theme files are automatically applied to the Extension Development Host window, so no reloading should be necessary.

Publish (internal)

Note: Publishing a new version of this theme is only meant for maintainers.

Prerequisite: Please follow this guide to install and login to vsce. Ask an existing maintainer how to get the "Personal Access Token".

  1. Merge any PR that is ready to be published into master.
  2. Update CHANGELOG.md + commit the changes.
  3. Run vsce publish [version]. Follow the SemVer convention and replace [version] with one of the following options:
    • patch for bug fixes
    • minor for improvements
    • major for breaking or bigger changes
  4. Push the commits and make a new realease.