Skip to content

fix: rename extension to git-identity-indicator to avoid marketplace name collision#3

Merged
seiya-koji merged 1 commit into
mainfrom
fix/rename-extension-id
Jun 29, 2026
Merged

fix: rename extension to git-identity-indicator to avoid marketplace name collision#3
seiya-koji merged 1 commit into
mainfrom
fix/rename-extension-id

Conversation

@seiya-koji

Copy link
Copy Markdown
Owner

Summary

Publishing to the VS Code Marketplace failed due to a name collision. This renames the extension id and display name to git-identity-indicator / Git Identity Indicator.

Background

  • The id git-identity-switcher is already taken by another publisher on the Marketplace.
  • The Marketplace requires the name field to be globally unique, which blocked publishing under the seiya-koji publisher (failed run).

Changes

  • package.json: namegit-identity-indicator, displayNameGit Identity Indicator, updated repository.url.
  • package-lock.json: synced the name field only, by hand (no changes to the platform-dependent dependency tree).
  • README.md: updated the H1 title, badges, and Marketplace link.
  • .devcontainer/devcontainer.json: updated name.
  • The GitHub repository has also been renamed to git-identity-indicator.

Release flow

After merge, release-please opens a v1.0.1 Release PR; merging that triggers CI to publish to the Marketplace automatically.

…name collision

The id "git-identity-switcher" is already taken by another publisher on the
VS Code Marketplace, which blocked publishing under the seiya-koji publisher.
Rename the extension id to "git-identity-indicator" and the display name to
"Git Identity Indicator". The GitHub repository has also been renamed
accordingly.
@seiya-koji
seiya-koji merged commit f8a918d into main Jun 29, 2026
2 checks passed
@seiya-koji
seiya-koji deleted the fix/rename-extension-id branch June 29, 2026 13:43
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