Skip to content

feat: add PaletteBot - automated VSCode theme change monitor - #4977

Draft
LiamM2004 wants to merge 8 commits into
mainfrom
feat/palettebot
Draft

feat: add PaletteBot - automated VSCode theme change monitor#4977
LiamM2004 wants to merge 8 commits into
mainfrom
feat/palettebot

Conversation

@LiamM2004

@LiamM2004 LiamM2004 commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds design-tokens/vscode_themes.json — the Figma variable collection for VSCode themes (2026 Light, 2026 Dark, HC Black) committed as the source of truth
  • Adds scripts/check-vscode-themes.mjs — fetches upstream VSCode theme files from microsoft/vscode, diffs them against the stored JSON, and updates it in place. Changes are grouped by component, filtered for case-only differences, and output as Markdown
  • Adds .github/workflows/vscode-theme-monitor.yml — PaletteBot workflow that runs on the 1st of every month, commits any changes, and posts a diff summary as a comment on a persistent tracking issue

How it works

PaletteBot runs monthly via GitHub Actions. If Microsoft changes any color tokens in the 2026 Light, 2026 Dark, or HC Black themes, PaletteBot:

  1. Updates design-tokens/vscode_themes.json automatically
  2. Posts a comment on the PaletteBot — VSCode Theme Changes tracking issue with changes grouped by component (e.g. button, editor, list) showing token name, old hex, and new hex

Designers can subscribe to the tracking issue to receive notifications. No secrets or external services required — uses the built-in GITHUB_TOKEN.

@hyperspace-pr-bot

Copy link
Copy Markdown
Contributor

The pull request is too large to be processed by Feature Automatic Summary:
Pull request has 73279 lines changed, which exceeds the maximum of 50000 lines.

PR Bot Information

Version: 1.29.2

  • Event Trigger: pull_request.opened
  • Correlation ID: 7f3b4fe0-8682-11f1-9a25-c889d22cf336

@changeset-bot

changeset-bot Bot commented Jul 23, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 40d0238

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

…, reorder steps, add commit link to issue comment
@sonarqubecloud

sonarqubecloud Bot commented Aug 5, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant