Forks: newgit tracker create --from

未关闭
#415 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
git, rust
领域
backend, cli

调研方向

Read the build order in #201, especially the comment titled “Roles are forks, exports live in definitions, and every tracker is a Git history,” and trace the tracker create command and serve storage model. Implement newgit tracker create <name> --role <role> --from <tracker> as a fork in the same store, enforcing that its audience is no wider than the upstream's. Done when the command creates the fork with that restriction; merging and --disclose belong to step 2.

由索引模型根据 Issue 内容生成。

描述

Step 1 of the build order in #201's comment Roles are forks, exports live in definitions, and every tracker is a Git history.

newgit tracker create staging-db --role db --from local-db starts a tracker at another tracker's history, so the members of a role share history and can merge with each other (tracker merge, rebase, cherry-pick; step 2). On serve a fork is a new ref namespace in the same store, so nothing is copied.

  • A fork's audience can't be wider than its upstream's.
  • Merging into a member with a wider audience needs --disclose, which lists what becomes readable. That's step 2 and can follow.
  • The same piece unlocks tracker mount <owner>/<tracker> later.

🤖 Generated with Claude Code

主要语言
Rust
星标
0
派生
0
平均合并
6 小时 21 分钟
30 天内合并 PR
173

环境准备

我们还没有检查这个项目的环境配置文件。先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Spheroman/newgit 的其他 Issue

查看 Spheroman/newgit 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。