Programming

22170 readers

177 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

Madeleine Mortensen: Jujutsu For Busy Devs (Part 1) (maddie.wtf)

submitted 1 week ago* (last edited 1 week ago) by HaraldvonBlauzahn@feddit.org to c/programming@programming.dev

38 comments fedilink hide all child comments

“Jujutsu (jj) is a version control system with a significantly simplified mental model and command-line interface compared to Git, without sacrificing expressibility or power (in fact, you could argue Jujutsu is more powerful). Stacked-diff workflows, seamless rebases, and ephemeral revisions are all natural with jj [...]”

Part 2 of the series is out and is here.

you are viewing a single comment's thread
view the rest of the comments

[–] atzanteol@sh.itjust.works 2 points 1 week ago (2 children)

I've started to tinker with it. "auto commit everything" is an absolute deal-breaker for me. There's no world in which I want every file I create to be added to source control without asking. I create lots of log files and other temp files when I work. Maybe I just fetched some .json from a service and put it in tmp.json? Maybe I created a small shell script to automate something I'm doing? I guarantee I'm going to end up pushing that shit upstream by accident at some point.

[–] ranting_sandfish@mander.xyz 2 points 1 week ago

Luckily you can turn it off and use the standard 'add' workflow. I did that almost reflexively when I started trying to use jj. (snapshot.auto-track)

However, over time, and once I got the .gitignore fully set up for bigger projects, I've come around on re-enabling autocommit for more of my repos. It does flow pretty naturally once you have an established process. I find it enables both better 'undo', and more seamless context-switching.

You can also set a more specific snapshot.auto-track on a repo or user basis for personal tooling conventions that don't make sense to gitignore.

[–] HaraldvonBlauzahn@feddit.org 1 points 1 week ago

I create lots of log files and other temp files when I work. Maybe I just fetched some .json from a service and put it in tmp.json? Maybe I created a small shell script to automate something I'm doing?

You might be able to put them into .gitignore. But why not keep the shell script in a tools folder?