From 026f8059831a9f9b79017ab6c2e97692b5f24104 Mon Sep 17 00:00:00 2001 From: philluiz2323 Date: Fri, 17 Jul 2026 17:09:32 -0300 Subject: [PATCH] docs(scripts): fix stale --db gittensory example in export-d1-data.mjs The usage comment at the top of scripts/export-d1-data.mjs still told a maintainer to run --db gittensory, the database name from before the 2026-07-15 repo rename. The real D1 database name (wrangler.jsonc's database_name) is now loopover, so copying the example as-is would target a database that no longer exists. Grepped the rest of the file for other stale gittensory-named examples; this was the only one. --- scripts/export-d1-data.mjs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/export-d1-data.mjs b/scripts/export-d1-data.mjs index f29ebc8f6e..5ef9c0912b 100644 --- a/scripts/export-d1-data.mjs +++ b/scripts/export-d1-data.mjs @@ -4,7 +4,7 @@ // a manifest the self-host importer validates against. The data transformation lives in export-d1-core.mjs (pure, // unit-tested); this file is the thin IO wrapper. // -// node scripts/export-d1-data.mjs --db gittensory --output ./export [--remote] [--since-date 2026-06-01T00:00:00Z] [--since-column updated_at] +// node scripts/export-d1-data.mjs --db loopover --output ./export [--remote] [--since-date 2026-06-01T00:00:00Z] [--since-column updated_at] // // --remote reads the deployed D1 (default is the local miniflare DB). --since-date does an INCREMENTAL export // (rows whose --since-column is >= the date); omit it for a full export. NEVER pass a write command.