{
  "id": 20853840,
  "title": "Jujutsu Primer",
  "url": "https://urgent.news/2026/11/20/jujutsu-primer",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-20T03:34:36.000Z",
  "source": {
    "name": "Lobsters",
    "slug": "lobsters",
    "url": "https://ethanlowman.com/posts/jj-primer/"
  },
  "original_language": "en",
  "account": "This guide introduces the Jujutsu version control system (jj) for those familiar with Git. jj provides simple yet powerful primitives for version control, such as automatic rebase and native undo. It can be used alongside Git in the same repository. To install jj, follow the official instructions or use common methods like using `pip` or `cargo`. Set user details globally with commands like `jj user name \"Ethan Lowman\"` and `jj user email \"ethan@example.com\"`. A commit, or revision, represents a snapshot of repository state with one or more parent snapshots. It can be visualized as a diff against a singular parent commit or multiple parent commits in a merge commit. Commit IDs are the same as Git commit IDs, while change IDs are stable identifiers for logical changes. Commit IDs and change IDs can be referenced using unique prefixes. JJ can inspect commits using commands like `jj show` and `jj status` shows repo state with diff stats. To create a new commit, use `jj new` or `jj desc`. JJ works similarly to Git diff, but with automatic snapshotting of the working copy. It organizes work streams through a graph of commits rather than branches, allowing for branching without creating named branches. Revsets, borrowed from Mercurial, are used to select sets of revisions from the commit graph.",
  "summary": null,
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}