From ef3f520f212b559eec1ad61b22cf877a2ab64d38 Mon Sep 17 00:00:00 2001 From: hoelee Date: Tue, 6 Oct 2026 17:26:08 +0800 Subject: [PATCH] =?UTF-8?q?post(upstream-rewrite):=20the=20wipe=20is=20ver?= =?UTF-8?q?ifiable=20in=20git=20=E2=80=94=20master=20is=20one=202026-06-22?= =?UTF-8?q?=20commit=20('deleted'),=20no=20common=20ancestor=20with=20main?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Re-checked against the actual repo rather than the API summary: the old branch survives as a single commit whose README is the word 'deleted', and it shares no common ancestor with main's 233 commits. Sharper and fully verifiable, EN+ZH. --- ...-upstream-was-deleted-then-came-back-rewritten.md | 12 +++++++----- ...-upstream-was-deleted-then-came-back-rewritten.md | 2 +- 2 files changed, 8 insertions(+), 6 deletions(-) diff --git a/src/content/posts/the-upstream-was-deleted-then-came-back-rewritten.md b/src/content/posts/the-upstream-was-deleted-then-came-back-rewritten.md index 6758b00..a5746c5 100644 --- a/src/content/posts/the-upstream-was-deleted-then-came-back-rewritten.md +++ b/src/content/posts/the-upstream-was-deleted-then-came-back-rewritten.md @@ -75,11 +75,13 @@ Verified on 2026-10-06, straight from the GitHub API and the registry: | Releases / tags | **0 / 0** | | Docker Hub | still **404** | -The 2021 history is gone. The `created_at` timestamp still reads 2021-08-13 -because GitHub keeps that field when a repository is re-populated, but the -git history begins on 2026-09-16 with an empty-repository commit. There is -also a ghost of the deletion still sitting on the old branch: fetch -`master`'s README and its entire contents are the single word `deleted`. +The 2021 history is there but disconnected. `main` carries 233 commits and +its oldest is dated 2026-09-16; the old branch survives as a **single commit +dated 2026-06-22** whose message is just `commit`, and whose entire README is +the one word `deleted`. The two branches share **no common ancestor** — which +is what a wipe followed by a fresh start looks like in git. (`created_at` +still reads 2021-08-13, because GitHub keeps that field when a repository is +re-populated; the history is what tells you the truth.) And the code behind those 233 commits is not my app's codebase continued. It is a different application that happens to keep the name: diff --git a/src/content/posts/zh/the-upstream-was-deleted-then-came-back-rewritten.md b/src/content/posts/zh/the-upstream-was-deleted-then-came-back-rewritten.md index 6168a96..e023cb1 100644 --- a/src/content/posts/zh/the-upstream-was-deleted-then-came-back-rewritten.md +++ b/src/content/posts/zh/the-upstream-was-deleted-then-came-back-rewritten.md @@ -48,7 +48,7 @@ draft: false | release / tag | **0 / 0** | | Docker Hub | 仍然 **404** | -2021 年那段历史没了。`created_at` 还显示 2021-08-13，只是因为 GitHub 在仓库被重新填充后保留了这个字段，但 git 历史是从 2026-09-16 一条空仓库提交开始的。被删除的痕迹还留在旧分支上：去取 `master` 的 README，全文只有两个字——`deleted`。 +2021 年那段历史还在，但已经断开了。`main` 上是 233 个提交，最早一条的日期是 2026-09-16；旧分支仍然存在，但只剩**一个提交，日期 2026-06-22**，提交信息就是 `commit`，而它的 README 全文只有一个词——`deleted`。两个分支**没有共同祖先**——这就是「先清空、再重来」在 git 里的样子。 而这 233 个提交里的代码，不是我原来那个代码库的延续。它是另一个应用，只是恰好沿用了同一个名字：