Skip to content
GitHub's VS Code theme
JavaScript
Branch: master
Clone or download

Latest commit

Latest commit 0bd9819 May 8, 2020

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.vscode Generate light theme Mar 24, 2020
src Merge pull request #13 from primer/active-selection May 7, 2020
themes Merge pull request #13 from primer/active-selection May 7, 2020
.gitignore Introduce theme generation to enforce use of Primer Colors Apr 23, 2020
.vscodeignore Generate light theme Mar 24, 2020
CHANGELOG.md Update CHANGELOG.md May 8, 2020
LICENSE Initial commit Mar 24, 2020
README.md Update screenshots + icon Apr 30, 2020
icon.png Update screenshots + icon Apr 30, 2020
package-lock.json 1.0.0 May 8, 2020
package.json 1.0.0 May 8, 2020

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. Press F5 to open a new window with your extension loaded
  3. Open Code > Preferences > Color Theme [⌘k ⌘t] and pick the "GitHub Light" or "GitHub Dark" 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.
You can’t perform that action at this time.