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

Abierto
#59 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
32/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
git, rust, tauri

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Rust
Estrellas
3
Forks
1
Merge medio
9 h 51 min
PR fusionados (30 d)
310

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de codeatlasdev/atlas

Todos los issues de codeatlasdev/atlas

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.