Repository navigation
refactor: replace GEI wording with "GitHub export" - #23
Merged
Merged
Conversation
The product surfaced "GEI" / "GitHub Enterprise Importer" in user-facing copy (README, API docs, the landing + profile pages, and one consideration summary) and throughout developer comments. Reframe everything around "the GitHub export" — what the export covers vs. what needs additional tooling — which is clearer for users who don't know the underlying importer's name. Also rename the exported constants GEI_DOC_URL -> MIGRATION_DOC_URL and GEI_DOCS_VERIFIED -> MIGRATION_DOCS_VERIFIED (and their test references). Left untouched: GitHub's real upload API path literals (/gei/archive, gei:// URIs) and historical CHANGELOG entries.
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.
What
Removes user-facing and developer-facing mentions of GEI / GitHub Enterprise Importer, reframing everything around "the GitHub export" — what the export covers vs. what needs additional tooling. Clearer for users who don't know the underlying importer's name.
Changes
User-facing copy
README.md— capabilities bulletdocs/api.md— Profile section introsrc/routes/+page.svelte— Profile workspace cardsrc/routes/profile/+page.svelte— Profile page subtitleconsideration-registry.ts— the "Repository Discussions" considerationsummary(shown in the Profile UI)Developer comments
analyze.ts,augment.ts,types.ts,github-ops.ts,github-ops.test.tsRenamed exported constants (+ their test references)
GEI_DOC_URL→MIGRATION_DOC_URLGEI_DOCS_VERIFIED→MIGRATION_DOCS_VERIFIEDLeft untouched (intentionally)
/gei/archive,gei://…URIs inupload.ts/upload.test.ts(these are GitHub's actual API surface, not branding)CHANGELOG.mdentriesVerification
bun run verify:json— all 11 gates green (coverage 86.49 / 84.56)GEI/GitHub Enterprise Importeroutside the two allowed categories above