Point the repository URL at tinbase/pg-mem after the transfer - #11
Merged
Conversation
The repo moved from sanketsahu/pg-mem to tinbase/pg-mem. GitHub redirects the old URL, so nothing was broken, but the package.json `repository` field is published to npm and would have kept sending people to the redirect - and 3.5.0 is not out yet, so this lands before anyone sees the stale one. Also repoints the README CI badge, which was rendering *upstream's* status (oguimbal/pg-mem) rather than this fork's, and via the old workflow-badge URL shape at that. It now shows this repo's own CI, which is worth having pointed somewhere true given it only started running at all today. Deliberately unchanged: - CONTRIBUTING.md's clone line for sanketsahu/pgsql-ast-parser. That repo has not moved (verified: tinbase/pgsql-ast-parser does not exist), so the reference is correct. Worth transferring too for consistency, but that is its own decision. - The remaining oguimbal links - wiki, FAQ, source examples - which legitimately point at upstream. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
The repo moved from
sanketsahu/pg-memtotinbase/pg-mem. GitHub redirects the old URL so nothing was broken, but two references were pointing somewhere stale.Changed
package.jsonrepository→https://github.com/tinbase/pg-mem. This one matters because it's published to npm, and it drives the "Repository" link on the package page. Good timing: 3.5.0 isn't published yet, so no release ever carries the stale URL.lib/package.jsoninherits it on build, verified.README CI badge. It was rendering upstream's status (
oguimbal/pg-mem/workflows/CI/badge.svg), not this fork's, and via the retired badge-URL shape. Now points at this repo'smain.yml. Worth having it point somewhere true, given CI only started running here today.Deliberately not changed
CONTRIBUTING.md's clone line forsanketsahu/pgsql-ast-parser. That repo has not moved — I verifiedtinbase/pgsql-ast-parserdoesn't exist — so the reference is correct as written. See below.oguimballinks (wiki, FAQ, source examples, the upstream PR reference). Those legitimately point at upstream and should stay, especially sincemasteris kept for eventually sending that PR.upstreamremote — stilloguimbal/pg-mem, unaffected.Verified
Tree clean,
bun testandbun typecheckpass,.denoregenerated (the readme copy changed with the badge, and is committed so the release gate stays green).Worth deciding separately
@tinbase/pg-memdepends onnpm:@tinbase/pgsql-ast-parser@^12.1.0, whose source repo is stillsanketsahu/pgsql-ast-parser. So there's now a scoped@tinbasepackage built from a personal repo. Transferring it to thetinbaseorg would make the pair consistent, and would mean the same "who owns the fork" answer for both. Not urgent and not something I'd do without you asking, but it's the one remaining split.