Desktop: Jujutsu (jj) workspaces as an alternative to git worktrees

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Find the existing git-worktree lifecycle behind the “New worktree” action and the Changes tab; that path is the model to mirror. Read how a worktree is created, diffed and deleted, then add a jj path that detects a colocated repo and shells out to jj workspace add, jj workspace list and jj workspace forget. Done means the three acceptance criteria hold: the new workspace appears in jj workspace list, deletion forgets it and removes the folder, and plain git repos behave as today.

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

描述

area: desktop status: needs-triage type: feature

Problem

jj users get parallel isolated checkouts through jj workspace add and prefer it over git worktrees; Atlas assumes git worktrees only.

Evidence

From research on parallel-agent desktops and worktree tools, this is a recurring user request:

A recurring request across agent-workspace and parallel-agent tools, with high upvote counts in their public trackers.

Proposed behavior

  • Detect a colocated jj repo; New worktree then uses jj workspace add and records the workspace.
  • Changes tab diffs the working-copy commit; delete uses jj workspace forget + folder removal.
  • Everything else (port offset, setup, agents) unchanged.

Acceptance criteria

  • In a jj repo, a new worktree is a jj workspace visible in jj workspace list.
  • Deleting it forgets the workspace and removes the folder.
  • Plain git repos behave exactly as today.
主要语言
Rust
星标
3
派生
1
平均合并
9 小时 51 分钟
30 天内合并 PR
310

环境准备

从这里开始

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

codeatlasdev/atlas 的其他 Issue

查看 codeatlasdev/atlas 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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