Rename project: seal -> docmend - #11
Merged
Merged
Conversation
The @seal npm scope was already taken by an unrelated party, so the whole project is renamed rather than just the tagline this time: - GitHub repo: dakshcodez/seal -> dakshcodez/docmend (gh repo rename; old URL auto-redirects) - npm packages: @seal/core -> @docmend/core, @seal/cli -> @docmend/cli, @seal/action -> @docmend/action - CLI bin command: seal -> docmend (npx docmend check/init/index) - Env vars: SEAL_GEMINI_API_KEY -> DOCMEND_GEMINI_API_KEY, SEAL_SKIP -> DOCMEND_SKIP - Ignore file: .sealignore -> .docmendignore (source file renamed too: packages/core/src/config/sealignore.ts -> docmendignore.ts) - Internal cache dir: .seal/ -> .docmend/ - All console log prefixes, action.yml name/branding, package.json names/descriptions/repository URLs, both READMEs, TESTING.md, .gitignore's comment about the committed action bundle "docmend" keeps the same self-heal wordplay spirit as the old name (doc + mend, mend being a close synonym for heal) - checked real npm registry and scope availability before landing on it, unlike "seal" originally. Verified with a full sweep for any remaining "seal" references across every tracked text file (zero found, including files with no extension like .gitignore that an earlier extension-filtered grep missed on the first pass) - not just the files touched by the substitution script. Verified runtime behavior, not just that it compiles: seal init's renamed CLI command produces a hook script that actually says "npx docmend check", and GeminiClient correctly reads DOCMEND_GEMINI_API_KEY while no longer recognizing the old SEAL_GEMINI_API_KEY name.
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
The
@sealnpm scope turned out to be already taken by an unrelated party. Rather than just renaming the tagline again, renamed the whole project to docmend (doc + mend — same self-heal wordplay spirit as "seal", checked real npm/scope availability this time before landing on it).Changed:
dakshcodez/seal->dakshcodez/docmend(already done viagh repo rename, old URL auto-redirects)@seal/core->@docmend/core,@seal/cli->@docmend/cli,@seal/action->@docmend/actionseal->docmendSEAL_GEMINI_API_KEY->DOCMEND_GEMINI_API_KEY,SEAL_SKIP->DOCMEND_SKIP.sealignore->.docmendignore(source file renamed:sealignore.ts->docmendignore.ts).seal/->.docmend/action.ymlbranding, package metadata, both READMEs,TESTING.md,.gitignore's commentTest plan
npm run lint/typecheck/buildall pass after re-runningnpm installto re-resolve the renamed workspace symlinks.gitignore, was missed on the first pass and caught on the second)docmend initproduces a hook script that actually containsnpx docmend check;GeminiClientcorrectly readsDOCMEND_GEMINI_API_KEYand confirmed the oldSEAL_GEMINI_API_KEYname is no longer recognized