Issues in the Repo
- ID: bed872f3
- 原文链接: https://nesbitt.io/2026/08/20/issues-in-the-repo.html
- 作者: Andrew Nesbitt
- 日期: 2026-08-20
- 来源类型: blog
- 标签: git, issue-tracking, forge, distributed, essay
- 质量评分: 3/5
- 抓取时间: 2026-08-20T15:44:49Z
中文导读
借 GitHub 周一数小时宕机，Andrew Nesbitt 系统综述了二十年来把 issue、PR、review 数据塞回 git 自身的五类方案：工作树内 issues 目录（Bugs Everywhere、ditz）、orphan branch（ticgit、haxy）、git notes（git-appraise）、自定义 ref namespace（git-bug、Gerrit NoteDb、Radicle）、内置 VCS（Fossil）。每类都附真实 git 命令输出，结尾演示 git bundle 把所有 custom refs 打包成单个 packfile，实现用 U 盘离线备份整个 forge。核心观点：代码在宕机时人人有克隆，而 issue 数据只存在于 GitHub 数据库里。
为什么值得关注
GitHub 宕机时的 Plan B 清单：五类把 issue 数据塞回 git 自身的方案与实战命令
原文摘录 (English Excerpt)
GitHub had a rough Monday this week, with git operations, Actions, and the issue tracker all unavailable for several hours. Code being unreachable during a forge outage is annoying but survivable because every contributor already has a full clone. Issues and pull request threads going dark is a different matter, since for most projects those exist only in GitHub’s database and nowhere else. I asked on Mastodon about tools that keep issue and review data inside the repository so it clones and pushes with the code, and got pointed at more projects than I expected, spanning about twenty years of people having a go at this.
The projects sort by where they physically put the data, and each storage location brings its own answers to the same handful of questions: whether a plain git clone fetches it, what happens when two people edit the same issue offline and then both push, wh
Obsidian 证据
- 来源 digest: AK RSS Digest 2026-08-20（2026-08-20，评分 8.5）
- 原文经 opencli web read / opencli arxiv paper 抓取核对，关键数字与摘要均锚定抓取内容。