I wrote up a Jujutsu workflow that I came up with recently. I wanted to work on a public open-source repository while also versioning the private context files that influenced each public commit: specs, product notes, experiments, and agent instructions.
I use coding agents heavily, which means the specs are often as important as the final code. I wanted a proper way to manage them without making them reachable from public history.
Jujutsu’s features give us a compact solution based on filesets, revsets, and `git.private commits`. With a small amount of code, this achieves a public/private split without much heavier tools like Copybara.
This is advanced material. It assumes intermediate jj knowledge, especially around revsets. Let me know what you think.
Comments
Hi HN,
I wrote up a Jujutsu workflow that I came up with recently. I wanted to work on a public open-source repository while also versioning the private context files that influenced each public commit: specs, product notes, experiments, and agent instructions.
I use coding agents heavily, which means the specs are often as important as the final code. I wanted a proper way to manage them without making them reachable from public history.
Jujutsu’s features give us a compact solution based on filesets, revsets, and `git.private commits`. With a small amount of code, this achieves a public/private split without much heavier tools like Copybara.
This is advanced material. It assumes intermediate jj knowledge, especially around revsets. Let me know what you think.