fix(config): scrub remaining pre-rename gittensory references - #6532
Merged
Conversation
The GitHub repo, npm scope, and directory paths were renamed to loopover, but several places still hardcoded the old JSONbored/gittensory identity: wrangler.jsonc's LOOPOVER_DRIFT_ISSUE_REPO/PUBLIC_REPO_STATS_ALLOWLIST vars (the self-repo config-as-code lookups resolve against a name GitHub only serves via redirect), release-selfhost.yml's github.repository == check (dead since the rename, silently disabling the Sentry-token release guard), gittensor-impact.yml's script arg, package.json repository/bugs/homepage URLs across the workspace, the website's GitHub-stats widget, two Grafana dashboard links/filter defaults, and the Sentry sourcemap upload's commit- linking fallback.
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Bundle ReportChanges will decrease total bundle size by 41 bytes (-0.0%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: loopover-uiAssets Changed:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6532 +/- ##
=======================================
Coverage 95.56% 95.56%
=======================================
Files 589 589
Lines 47121 47121
Branches 14989 14989
=======================================
Hits 45032 45032
Misses 1297 1297
Partials 792 792
Flags with carried forward coverage won't be shown. Click here to find out more. |
2 tasks
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
1 participant
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
wrangler.jsonc:LOOPOVER_DRIFT_ISSUE_REPO,PUBLIC_REPO_STATS_ALLOWLIST, andLOOPOVER_PUBLIC_STATS_REPOSstill hardcoded the pre-renameJSONbored/gittensoryrepo identity (GitHub only serves that name via redirect now);worker-configuration.d.tsregenerated to match.LOOPOVER_PUBLIC_STATS_REPOSkeeps the old name alongside the new one since that var's own doc comment explains it exists specifically to preserve historical pre-rename rows..github/workflows/release-selfhost.yml:if: github.repository == 'JSONbored/gittensory'has been dead since the rename (github.repositoryreadsJSONbored/loopover), silently disabling the "require Sentry token for an official release" guard..github/workflows/gittensor-impact.yml: the README impact-card script was still passed the old owner/repo pair.package.json(root + the 4 published@loopover/*sub-packages): stalerepository/bugs/homepageURLs..github/ISSUE_TEMPLATE/config.yml: contact-link URLs pointed at the old repo.apps/loopover-ui/src/components/site/github-stats-chip.tsx(+ test): the website's own GitHub stars/forks widget queried stats for the old repo name.grafana/dashboards/github-prs.json/resource-hub.json: a dashboard doc link, and a template-variable default that would otherwise pre-select a repo name absent from live data.review-enrichment/src/upload-sourcemaps.ts(+ test): the Sentry commit-linking (--commit owner/repo@sha) fallback used the old repo — distinct from the Sentry project/monitor slug naming that issue Sentry project and monitor migration (self-host error tracking) #5333 deliberately keptgittensory-prefixed for alert-continuity reasons, which this PR does not touch.Discovered while investigating a flagged flaky-by-real-network unit test; the actual test-isolation bug and the migration-0156 collision both turned out to already be fixed on
mainby #6493 and #6494, which landed while this was in progress — this PR is only the remaining stale-reference residue those didn't cover.Validation
npm run typecheck,npm run actionlint,npm run cf-typegen:check— all greennpx vitest run(full suite, unsharded): 17,536 passed, 0 failednpm run rees:test(review-enrichment): 1,335 passednpm --workspace @loopover/ui run test: 283 passed