VSCode Theme based on the colour scheme of my portfolio
Go to file
Daniel Castillo e5b18427cf
exclude source files and node_modules from extension bundle
2020-05-17 15:38:04 +02:00
.vscode Trigger build before running extension 2020-05-17 15:36:34 +02:00
src parallelize writing files 2020-05-17 15:36:57 +02:00
.gitignore exclude source files and node_modules from extension bundle 2020-05-17 15:38:04 +02:00
.vscodeignore exclude source files and node_modules from extension bundle 2020-05-17 15:38:04 +02:00
CHANGELOG.md Update CHANGELOG.md 2020-05-16 00:41:26 +09:00
LICENSE Initial commit 2020-03-24 14:07:31 +09:00
README.md make sure to npm install before running extension in docs 2020-05-17 15:37:21 +02:00
icon.png Update screenshots + icon 2020-04-30 12:27:48 +09:00
package-lock.json 1.1.1 2020-05-16 00:41:52 +09:00
package.json 1.1.1 2020-05-16 00:41:52 +09:00

README.md

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. Run npm install to install the Primer CSS color reference and run npm start to run the converter.
  3. Press F5 to open a new window with your extension loaded
  4. Open Code > Preferences > Color Theme [⌘k ⌘t] and pick the "GitHub Light" or "GitHub Dark" theme
  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 release.