fix(ci): update remaining gittensory references in workflow files - #6876
Merged
Conversation
release-selfhost.yml carried a real bug, not just stale naming: with
SENTRY_PROJECT unset as a repo variable, every release build fell back to
the hardcoded default 'gittensory' -- the Sentry project's pre-rename
slug -- and stamped SENTRY_RELEASE/LOOPOVER_VERSION with
"gittensory-orb@${VERSION}" on every single release, which is exactly
the stale value found and removed from the server's .env earlier this
session. Fixed the job-level default, the 3 step-level fallbacks, and
the release-string template so future releases stop regenerating it.
selfhost.yml and visual-capture-fallback.yml had only cosmetic
CI-ephemeral identifiers (a throwaway test Postgres DB name, Docker
image tags scoped to a single job run) and prose comments describing
current backend behavior -- updated for consistency. The two
pre-rename-framed historical comments in release-selfhost.yml
documenting a past Docker-image-name decision (#4777) are left
untouched, same as everywhere else this session.
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
3 tasks
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
luciferlive112116
pushed a commit
to luciferlive112116/gittensory
that referenced
this pull request
Jul 17, 2026
…y release default deploy-selfhost-prebuilt.sh carried the same live bug just fixed in release-selfhost.yml (JSONbored#6876): SENTRY_RELEASE defaulted to "gittensory-selfhost@<sha>" when unset, so a manual/prebuilt deploy would tag Sentry with the pre-rename project's release format on every run. Fixed the default, its log-file path, and the usage-example comment. check-changelog.mjs's temp-dir prefix, export-ams-reporting-db.sh's "AMS (gittensory-miner)" comment, and export-miner-prometheus-textfile.sh's default output filename were cosmetic-only -- updated for consistency with the already-renamed LOOPOVER_MINER_* env vars around them. Deliberately left untouched (verified each is either external or a separate, real, current convention, not gittensory-rebrand drift): export-d1-core.mjs's [[gittensory-selfhost-migration-plan]] wiki-link (can't verify the target doc's real name from here); export-d1-data.mjs's `--db gittensory` usage example (confirmed against the live Cloudflare account: the production D1 database is genuinely still named "gittensory", by explicit decision -- no rename planned, D1/R2 have no in-place rename support and the cost of a live-data migration isn't worth it for a cosmetic label); export-grafana-reporting-db.sh's 'gittensory-native' source-column literal (a stored, historical DB discriminant value, must stay stable for existing rows); gittensor-impact-card.mjs (calls the unrelated external gittensor.io service); github-type-label.d.mts and the config it mirrors (gittensor:bug/feature/priority are real, current GitHub label names on this repo, a deliberate naming choice separate from the old gittensory product name); and selfhost-post-update-check.sh's historical comment about the rename incident itself.
luciferlive112116
pushed a commit
to luciferlive112116/gittensory
that referenced
this pull request
Jul 17, 2026
…tes, env examples, release.yml, and this repo's own skill files - .github/release.yml: gittensory-orb[bot] doesn't exist anymore (confirmed 404 against the GitHub API) -- the real, current bot login is loopover-orb[bot]. - .env.example: updated a comment that documented the exact stale SENTRY_RELEASE/LOOPOVER_VERSION default already fixed in JSONbored#6876/JSONbored#6881 -- it was telling self-hosters "yes, still that prefix", which is no longer true. - .env.selfhost.example: example GITHUB_APP_SLUG value and a prose line describing the telemetry collector. - .claude/skills/contributor-pipeline-gardening/{SKILL,reference}.md: this repo's own scheduled-task skill had a real, executable `gh issue list --repo JSONbored/gittensory` command. It still resolves today via GitHub's rename redirect, but relying on that indefinitely is fragile and exactly the kind of stale reference that confuses a future AI session working in this repo. Fixed the command and simplified two section titles. - n8n/workflows/*.json: 3 bundled workflow templates (not currently deployed -- profile "workflows" isn't in this fleet's active COMPOSE_PROFILES) had gittensory-prefixed names, webhook paths/ids, and suggested env var names. Confirmed nothing in src/scripts/tests references these specific webhook paths or env vars before renaming, and kept each node-name rename in sync with its connections-object key. Left untouched: gittensor:bug/feature/priority (the real, current GitHub label convention, unrelated to the old gittensory product name) and gittensor-deployment-models (a cross-reference to this session's own memory-file slug, out of scope for a repo-code change).
3 tasks
bitfathers94
pushed a commit
to bitfathers94/loopover
that referenced
this pull request
Jul 17, 2026
…er-ui, loopover-ui, and loopover-miner-extension - CLI command references in comments (governor.ts, portfolio-queue-actions.ts, vite-portfolio-queue-api.ts) still said `gittensory-miner ...`; the real binary is `loopover-miner` (confirmed against package.json's own bin field). - 9 vite-*-api.ts dev-server plugins had their `name:` field (and chat-api.test.ts's matching assertion) as `gittensory-miner-ui:...`. - vite.config.ts's port-offset comments and styles.css's design-system comment referenced the sibling app as `gittensory-ui`; confirmed loopover-ui's own vite config relies on the same default ports (5173/4173) the comments describe. - self-hosting-operations.mdx documented the exact stale SENTRY_RELEASE/ LOOPOVER_VERSION default already fixed in JSONbored#6876/JSONbored#6881/JSONbored#6888 as current behavior ("defaults to gittensory-selfhost@..."). - packages/loopover-mcp/bin/loopover-mcp.js had a comment claiming "enrichment-analyzers keeps its legacy gittensory:// URI on purpose" -- stale since JSONbored#6786 actually renamed that URI to loopover://. - Remaining ~50 occurrences (background.test.ts, opportunity-badge.test.ts, governor/ledgers/portfolio-queue-*.test.tsx's mock config-dir paths, proof-of-power-stats.test.tsx, browser-sentry.test.ts) were all arbitrary placeholder fixture values -- confirmed each by reading the source under test: browser-sentry.ts's VITE_SENTRY_RELEASE has no hardcoded default at all (pure passthrough, not the JSONbored#6876-class bug), so its test fixture value is genuinely arbitrary, same as the repo-name/path fixtures elsewhere. Left untouched (verified real, not drift): try-it.ts/.test.ts's LEGACY_STORAGE_KEY = "gittensory.session_token" and the matching legacy-key arguments in app.index/runs/workbench.tsx's useLocalStorage(new, default, legacy) calls -- this is a deliberate migration path so a returning user's existing browser localStorage (session token, onboarding state, saved views, workbench tab) is still recognized after the rebrand. Also left the 3 self-hosting docs' "Renamed from gittensory-selfhost" / "pre-rename name" callouts, which are already correctly historically framed. All affected test suites pass: 98 (miner-ui) + 29 (loopover-ui) + 16 (miner-extension) = 143 tests, plus a clean loopover-miner-ui typecheck.
thomasalvaedison7777-lgtm
pushed a commit
to thomasalvaedison7777-lgtm/loopover
that referenced
this pull request
Jul 17, 2026
…ry references src/sentry.ts's resolveReesSentryRelease() defaulted every REES release id to "gittensory-rees@<sha>" when SENTRY_RELEASE wasn't set -- same live bug class as JSONbored#6876/JSONbored#6881, this time in REES's own separate Railway deploy rather than the main app. Fixed the default and every test/doc reference describing that exact format (README.md's Sentry setup guide, sentry-upload/sentry-release-validation/sentry-degradation tests). The remaining ~70 occurrences across analysis-context, analyzer-registry, analyzer-circuit-breaker, external-fetch, render-contract, request-guardrails, and scheduler tests were all an arbitrary "JSONbored/gittensory" placeholder repoFullName fixture value -- any string works equally to test that logic, so this is a consistency-only cleanup, not a bug fix. analyzer-circuit-breaker.test.ts's casing REGRESSION test ("jsonbored/gittensory" vs "JSONbored/Gittensory") preserves the exact same casing-variation relationship with "jsonbored/loopover" / "JSONbored/Loopover". Left untouched: GITTENSORY-15 (a Sentry ticket id, permanent regardless of the project rename) and two historical PR/issue citations in secret-scan.ts/.test.ts ("gittensory PR JSONbored#5346/JSONbored#5341", "metagraphed/gittensory#4524") -- PR/issue numbers are stable identifiers independent of a repo rename, and the second one's cross-repo shape wasn't clear enough to edit with confidence. All 1335 review-enrichment tests pass.
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
release-selfhost.ymlcarried a real bug, not just stale naming:SENTRY_PROJECTisn't set as a repo variable (confirmed viagh variable get), so every release build was falling back to the hardcoded default'gittensory'— the Sentry project's pre-rename slug — for all Sentry API calls. Separately, therelease=gittensory-orb@${VERSION}step output feedsSENTRY_RELEASE(3 places) andLOOPOVER_VERSIONon every release, meaning this workflow was actively regenerating the exact stale value I found and removed from the server's.envearlier this session, not just leaving an old leftover. Fixed the job-level default, all 3 step-levelvars.SENTRY_PROJECT ||fallbacks, and the release-string template.selfhost.ymlandvisual-capture-fallback.ymlhad only cosmetic references: a throwaway CI-only test Postgres DB name, Docker image tags scoped to a single job run, and prose comments describing current backend behavior. Updated for consistency/clarity.release-selfhost.yml(lines 8, 224) that correctly document a past Docker-image-naming decision (Retire every deprecation shim #4777) in historical-past-tense framing — those are legitimate history, not drift.Scope
Validation
npm run actionlint— cleangit diff --check— cleangit grepthat only the 2 legitimate historical comments remain across all 3 files