xintron
Joined 14 years ago
Joined 14 years ago
With jj, your working copy is always a commit. This encourages a "commit often and messy, clean up later" approach. You can rapidly iterate with or without AI, letting jj automatically save every change without stopping to craft perfect atomic commits.
Later, you use a simple jj squash to combine all those small, iterative changes into logical, clean commits before you share it. The atomicity is created retroactively, not upfront. For a finely-tuned magit workflow this might feel wrong, but for rapid, exploratory and AI-driven iteration, it's a more natural fit.
Custom settings depending on the environment you're in, here setting up PowerShell on windows only. Allowing the same flexibility through JSON/YAML would not be as easy and simple.
It depends on what you're doing. For documentation I'm always running reST but for articles for sites etc (with a static site generator) I will turn to Markdown.