Repository navigation
chore: move from tester-army to e2e-inc GitHub org - #10
Merged
Merged
Conversation
KrzysztofMoch
approved these changes
Nov 12, 2026
szymonrybczak
approved these changes
Nov 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update GitHub references after the organization moved on 10 November 2026.
Changed files:
.claude-plugin/marketplace.json.claude-plugin/plugin.json.codex-plugin/plugin.json.cursor-plugin/plugin.json.github/workflows/publish-mcp-registry.ymlREADME.mdplugin.jsonscripts/check-plugin-manifests.shserver.jsonLeft intentionally
Historical changelogs, npm names/scopes, existing product branding and tester.army domains/emails are unchanged.
Registry identity intentionally changes from
io.github.tester-army/testerarmytoio.github.e2e-inc/testerarmy. This is a NEW registry entry, not a rename of the old entry. Nothing was published here. The existing main-branch publish workflow will publish the new identity after merge; review that release decision before merging. Plugin IDs and hosted MCP URL stay unchanged.Verified
Ran it locally: yes, static validation.
git diff --checkpassed; changed JSON files parse. Reviewed the diff and searched tracked files for remaining old-org references. No application runtime changed; full app builds/device suites were not run for link/documentation-only changes.bash scripts/check-plugin-manifests.shpassed from the repository root.