Release v0.34.0 · jj-vcs/jj
Release v0.34.0 · jj-vcs/jj
github.com
Release v0.34.0 · jj-vcs/jj
4 comments
-
-
i really want to get into
jjcuz i like the pitch, but the real struggle isn’t new syntax or learning curve but the fact that my workflows at home and especially at work are built around git and GitOps. i tried briefly to integrate it into my dotfiles, but migrating such a large repository got a little hairy.is there a doc about why a seasoned pro (at least don’t tell my manager otherwise) would switch to
jj? are people using this in production effectively? is there a world where i can integratejjinto existing git based workflows that interact seemlessly with other contributors using plain ole git?-
jjis built on top of Git. If you use "colocated" repositories (which is now the default), your Git workflows will still work. In fact, all my Nvim setup with Git plugins didn't need any change. When your runjjcommands, they will operate on the Git repo, and if you run Git commands, they will be imported byjjas needed. I've been using almost exclusivelyjjat work and in open-source contributions, and so far no one has noticed (why should they).As to why you should use it, let's say that it encourages you to have a better development workflow, a cleaner Git history, and an easier time working on top of code that is being reviewed, by lowering the barrier. Rebase is easier to use, absorb and squash are a godsend for keeping a clean history, and a lot of design decisions that, when you think about it, just makes sense from a usability perspective.
I encourage you trying it out, I certainly don't regret it, it does feel a lot easier to use than bare Git.
-
no one has noticed
nice. this is a detail that i needed to know that would otherwise be a dealbreaker.
i am intrigued by the promises of better histories, since i’ve been reviewing and contributing to a bunch of repos at work.
a lot easier to use
see this is the issue. i don’t find git hard to use. and i’m not going to be one of those assholes that’s like “i never thought it was hard”; i’ve just genuinely been at this for over a decade now. and i run
nushellso i’m not opposed to new niche things as long as it improves my workflow.i’ll have to check it out again.
-
-
Hrm, the pre-commit issue is still open.
Like the others in that thread, I'm not married to pre-commit or the check happening before the commit as opposed to the push, I just want to have some easy-to-setup, standardized way of preventing myself from pushing stuff that will be rejected by CI.