8000 GitHub - nurul3101/github-vscode-theme at v0.2.3
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

nurul3101/github-vscode-theme

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

56 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

< 773A div class="markdown-heading" dir="auto">

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. Make changes to the /themes/light.json 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.
  5. 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.

Packages

No packages published

Languages

  • JavaScript 100.0%
0