I use jj workspaces extensively, to be able to let various things work on trees in parallel. jj workspaces and Git colocation are not in a great place. The non-default jj workspaces don't get a .git which ~breaks a variety of tools and scenarios, including some around Nix.
The pre-commit hook isn't a great fit for jj because of Always Be Committing, but we think pre-push solves the same use cases. You can achieve something like that today with jj run:
Converge looks great, but the reason I have divergent commits to converge in the first place is when I forget you can’t use workspaces in parallel. So I’m hoping when the worktree support comes out, I won’t need converge!
We weren't able to publish the 0.45.0 crates because we had the category "version-control" in Cargo.toml, and apparently that's no longer allowed on crates.io. This was a problem for this release because we created a new jj-core crate.
Rather than publish a different commit than the git tag, we chose to make a 0.45.1.
Would cargo publish --dry-run catch that, or is that done entirely on the remote side after uploading? (I'm unsure offhand if --dry-run includes any communication at all with the registry)
hunger | 17 hours ago
Jj releases are really getting boring... Lots of polish and small things that make live easier, but very few things to get excited about.
I love that :-) Shows how far they have come and how stable the thing got in the meantime.
jennings | 10 hours ago
Do you have anything on your wishlist that you would find exciting?
colemickens | 8 hours ago
I use jj workspaces extensively, to be able to let various things work on trees in parallel.
jjworkspaces and Git colocation are not in a great place. The non-default jj workspaces don't get a.gitwhich ~breaks a variety of tools and scenarios, including some around Nix.I think this is non-trivial and I'm told Caleb is working on it, but it's a pretty decent thorn in my side: https://github.com/jj-vcs/jj/issues?q=is%3Apr+is%3Aopen+author%3Acalebdw
offby1 | 8 hours ago
I'm not the OP but... hook support is my big dream.
jennings | 8 hours ago
The
pre-commithook isn't a great fit for jj because of Always Be Committing, but we thinkpre-pushsolves the same use cases. You can achieve something like that today withjj run:It's not the most ergonomic thing, but is this approximately what you want to do with hooks?
hunger | 6 hours ago
Something like commit hooks -- not easy with jj's model -- would be great.
But I am actually very happy with jj, and all the polish it gets:-)
nwjsmith | 2 hours ago
Pluggable backends.
aaronmallen | an hour ago
Pushing tags would be pretty cool ngl
fedemp | 15 hours ago
If hope this comes in handy when my branch is rebased in the remote and my local branch was updated.
wrs | 10 hours ago
Converge looks great, but the reason I have divergent commits to converge in the first place is when I forget you can’t use workspaces in parallel. So I’m hoping when the worktree support comes out, I won’t need converge!
asem | 7 hours ago
a dot release just released hours later https://github.com/jj-vcs/jj/releases/tag/v0.45.1
jennings | 7 hours ago
We weren't able to publish the 0.45.0 crates because we had the category "version-control" in Cargo.toml, and apparently that's no longer allowed on crates.io. This was a problem for this release because we created a new
jj-corecrate.Rather than publish a different commit than the git tag, we chose to make a 0.45.1.
lilyball | 6 hours ago
Would
cargo publish --dry-runcatch that, or is that done entirely on the remote side after uploading? (I'm unsure offhand if--dry-runincludes any communication at all with the registry)