---
title: "The GitStudio blog — shipping developer tools in the open"
description: "Field notes from building GitStudio: publishing to the VS Code Marketplace and Open VSX, fighting content filters, and shipping tools in the open."
url: https://gitstudio.dev/blog/
---

The blog

# Built in the _open._

Field guides and war stories from shipping GitStudio — the publishing pipelines, the marketplace landmines, and everything Microsoft finds “suspicious”.

- [Jun 22, 2026](https://gitstudio.dev/blog/how-to-publish-a-vscode-extension-on-both-marketplaces/)
  ## [How to publish a VS Code extension on both marketplaces](https://gitstudio.dev/blog/how-to-publish-a-vscode-extension-on-both-marketplaces/)
  [A complete, no-gaps guide: build, publish, get approved, and get verified on the VS Code Marketplace AND Open VSX — including how to choose a publisher name that the content filter will actually accept.](https://gitstudio.dev/blog/how-to-publish-a-vscode-extension-on-both-marketplaces/)

  [Read the post](https://gitstudio.dev/blog/how-to-publish-a-vscode-extension-on-both-marketplaces/)
- [Jun 22, 2026](https://gitstudio.dev/blog/microsoft-said-my-name-was-suspicious/)
  ## [Microsoft said my name was "suspicious content"](https://gitstudio.dev/blog/microsoft-said-my-name-was-suspicious/)
  [What the VS Code Marketplace "Publisher Metadata has suspicious content" error actually is, how I figured it out after days of fighting it, and why the support reply is a rubber stamp. Plus: Open VSX is quietly the bigger marketplace.](https://gitstudio.dev/blog/microsoft-said-my-name-was-suspicious/)

  [Read the post](https://gitstudio.dev/blog/microsoft-said-my-name-was-suspicious/)