fix(rebrand): full-cutover rename remaining internal gittensory runtime identifiers - #5761
Merged
Conversation
…me identifiers Phase 8a of the rebrand epic (#5705): renames functional runtime identifiers that survived Phases 1-7 because they weren't caught by prior sed/perl sweeps (bare positional-argument actor strings, object keys, Sentry context/fingerprint names, OTel span attributes, HKDF/hash namespace strings, extension message-passing protocol strings and CSS class names, and the miner's worktree branch prefix/subdir). Also fixes two regressions/drift discovered along the way: - apps/loopover-extension/content.js's data-attribute duplicate-mount guard was querying the old gittensory-prefixed attribute name after Phase 6 renamed the setter, silently disabling the guard. - packages/loopover-miner/docs/env-reference.md's checked-in title was stale against its Phase-5-fixed generator. - apps/loopover-ui's docs.gittensory-commands.tsx route file (and its footer/nav links) were never renamed even though the @Loopover mention-command docs it covers already were (Phase 2), leaving a stale /docs/gittensory-commands URL in every bot comment footer. Deliberately NOT touched: the real (unrenamed) JSONbored/gittensory GitHub/Sentry-project references, GITTENSORY_LEGACY_* check-run constants, the already-decided gittensory-selfhost container-image legacy alias, the PUBLIC_SITE_ORIGIN_ALIASES domain alias, and the .gittensory-miner.yml per-repo config filename (separate, large, deferred to its own follow-up).
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5761 +/- ##
=======================================
Coverage 95.07% 95.07%
=======================================
Files 581 581
Lines 46181 46181
Branches 14811 14811
=======================================
Hits 43905 43905
Misses 1516 1516
Partials 760 760
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
This was referenced Jul 14, 2026
Closed
Closed
Closed
This was referenced Jul 15, 2026
Closed
Closed
Closed
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.
Summary
apps/loopover-extension/content.js's duplicate-mount guard was querying the pre-Phase-6 attribute name after the setter was renamed, silently disabling the guard.packages/loopover-miner/docs/env-reference.md(title never regenerated after Phase 5 fixed the generator).apps/loopover-ui's/docs/gittensory-commandsroute (file + URL + footer/nav links) was left stale even though the@gittensory→@loopovermention-command docs it covers were already renamed in Phase 2 — every bot comment footer was linking to a URL that no longer matched the feature name.Deliberately not touched (confirmed permanent/deferred):
JSONbored/gittensoryGitHub repo and Sentry-project referencesGITTENSORY_LEGACY_*check-run constantsgittensory-selfhostcontainer-image legacy aliasPUBLIC_SITE_ORIGIN_ALIASESdomain alias.gittensory-miner.ymlper-repo config filename — a large (37-file), distinct surface, deferred to its own follow-up PRTest plan
npm run typecheckcleannpx vitest run— 837 files / 16251 tests passed (2 pre-existing skips)npm run test:cigate green end-to-end (migrations, schema-drift, env-reference, actionlint, engine/mcp/miner builds+packs, docs/manifest/engine-parity drift, UI lint/typecheck/test/build)apps/loopover-ui/public/openapi.jsonandrouteTree.gen.tsafter source changes