Was it evaluated how nice `gt` cooperates with `jj...
# how-do-iv
Vampire
04/20/2026, 10:19 PMWas it evaluated how nice
gtjjgtjj✅ 1
p
Pylon
04/20/2026, 10:19 PM(If applicable) To help us more clearly understand what you're trying to do, please provide additional details about:
- Screenshots / debug logs / list of commands you've tried to run so far
- Your workflow
- Current state
v
Vampire
04/20/2026, 10:20 PMNo, it's not applicable 🙂
p
Pylon
04/21/2026, 1:12 PMBjörn, thanks for raising this. We currently have a feature request ticket in place to support
jjv
Vampire
04/21/2026, 1:21 PMThanks, I did not yet try to use gt with jj together.
In a colocated repository it will probably work somehow as it is at the same time a Git repository.
But in non-colocated repository or one that does not use the Git backend, dedicated jj support will be necessary.
👍 1
s
Sean McKenna
04/21/2026, 3:33 PMI'd doubt native jj support would be something they would consider, and that wouldn't work for GitHub today anyway.
Sean McKenna
04/21/2026, 3:36 PMBoth can interoperate with git in colocated mode, so you can use them both. Not sure if it's gotten better, but commands like gt rebase/reorder/sync may all wipe the change IDs (that would be good to fix).
I've been using jj for most of my development (including pushes and anonymous branches) and only gt track/submit when I need to open a formal stack to link the PRs automatically.
The auto rebase of a stack in the cloud after a merge would also cause issues for me, so I usually rebase myself and so have to set my bookmark again to push over it. (Friction)
v
Vampire
04/21/2026, 4:11 PMThanks for your experience report.
and that wouldn't work for GitHub today anywayYeah, true, if not Git-backed. But if Git-backed but not colocated, or in a jj workspace which do not yet support colocation, native jj support might be necessary and work, and if it "just" is to get the git repo dir from jj to work with. While using native jj commands might work better from jj PoV.
❤️ 1
s
Sean McKenna
04/21/2026, 4:38 PMI'm trying to remember how well graphite handles work trees even. I tend to use gt from the main repo.
jj has tickets and plans for co located worktrees. idk if it would be separate from workspaces or not. Graphite is very much coupled with git though, and the fact that jj "native" has git under the hood today is a design detail. They have also talked about having their own custom built data store. I feel like they've not officially recommended assuming git is there internally 😆
v
Vampire
04/21/2026, 4:57 PMWell, jj does already run without Git.
Inside Google, there they have a distributed database as backing store or something like that.
Currently for "normal" users like us the Git backend is the only production-ready one, yeah, but that might change over time.
But of course then gt does not need to be compatible as long as it "only" supports GitHub 😄
👍 1