jj

To manage stacked commits with automatic rebasing, you need a version control system where the working copy is a commit. This approach eliminates manual staging by continuously snapshotting changes and automatically rebasing dependent commits.

Revsets are an expressive query language for precise commit selection in large histories. They allow you to flexibly query and select commits based on complex conditions, making history navigation highly efficient.

Yes, Jujutsu provides seamless Git interoperability. It operates within the Git environment without requiring external tooling, allowing you to manage multi-branch collaboration and complex histories using change IDs.

You can undo version control operations using a built-in operation log. This feature tracks state changes over time, enabling safe undo and redo actions when automatic rebasing produces unexpected results.

First-class conflict handling allows merge conflicts to exist within commits without blocking your workflow. This means you can continue working and even commit while conflicts are still being resolved.

The best way to track changes without a staging area is using a working-copy-as-commit model. You can quickly start by creating a new change with a message, describing it, and viewing the operation log.