tumble
/
tumble-yellow-dark-vscode
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 2 Wiki Activity
VSCode Theme based on the colour scheme of my portfolio
254 Commits 5 Branches 28 Tags 730 KiB
JavaScript 100%
Go to file
simurai 66f9446a83 4.1.1 2021-04-28 23:39:25 +09:00
.vscode Trigger build before running extension 2020-05-17 15:36:34 +02:00
src Merge pull request #167 from misolori/master 2021-04-28 23:23:57 +09: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 2021-04-28 23:38:41 +09:00
LICENSE Initial commit 2020-03-24 14:07:31 +09:00
README.md Update README.md 2021-04-14 15:32:45 +09:00
icon.png Update screenshots + icon 2020-04-30 12:27:48 +09:00
package-lock.json 4.1.1 2021-04-28 23:39:25 +09:00
package.json 4.1.1 2021-04-28 23:39:25 +09:00

README.md

GitHub's VS Code themes

GitHub VS Code theme

Install

  1. Go to VS Marketplace.
  2. Click on the "Install" button.
  3. Then select a theme. Currently the following themes are available:
    • GitHub Light
    • GitHub Dark
    • GitHub Light Default ✨ new ✨
    • GitHub Dark Default ✨ new ✨
    • GitHub Dark Dimmed ✨ new ✨

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. Run npm run build to generate the themes with the new changes.
  3. Update CHANGELOG.md + commit the changes.
  4. 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
  5. Push the commits and make a new release.