using-jj-instead-of-git

You can replace git commands with jj equivalents for version control by mapping standard actions like commit, amend, branch, and rebase to Jujutsu's syntax. This workflow provides automatic file tracking and a simpler mental model while remaining Git-compatible.

The best way to manage branching and merging in jj is by using bookmarks instead of traditional branches. This approach simplifies history editing through squash, split, and operation log undo, avoiding destructive resets while maintaining remote interoperability.

Yes, you can push and fetch to existing Git remotes using jj. Jujutsu maintains full remote interoperability with Git, allowing you to manage bookmarks and synchronize changes without losing compatibility with your current repository infrastructure.

You should use jj instead of git for editing commit history to leverage safer, non-destructive operations. Jujutsu's operation log with undo, alongside squash and diffedit, lets you adjust changes without the risk of complex rebases or hard resets.

Yes, jj supports cherry-picking and amending commits like git. It provides direct equivalents for these version control actions, allowing you to amend changes seamlessly while relying on automatic change tracking instead of manual staging.

You should not switch from git to jj if your team relies on highly specific Git hook configurations or commands lacking direct jj equivalents. While jj covers standard version control tasks, complex custom Git pipelines may require staying within native Git.