The Undocumented Stack

📁 Files

src/login.ts

src/logout.ts

src/session.tsA

A NewM Modified

JJ Log

◆ zzzzzzzz Learner 2026-06-17 08:35:47 00000000 root()

○ wdesc01 Learner 2026-06-17 08:35:52 dddd1111

│ (no description set)

○ wdesc02 Learner 2026-06-17 08:35:57 dddd2222

│ (no description set)

@ wdesc03 Learner 2026-06-17 08:36:07 dddd3333

│ (no description set)

JJ Graph@ wdesc03

✂️ The Messy Commit0/6

📖 Story

Monday morning your tech lead pings you: 'Can you split that PR? It touches auth AND the cart — I can't review both at once.' In Git this means reset, stash, branch, cherry-pick chaos. In jj you just split.

Check the log: jj log

You have one change called 'Add auth and cart' that added two unrelated files. Your lead wants two separate changes. Let's split it.

● Check the log: `jj log`

○ Split the change: `jj split wmess02`

○ Describe part 2 (WC's parent): `jj describe -m "Add cart" -r @-`

○ Describe part 1: `jj describe -m "Add auth"`

○ Verify: `jj log`

○ Bonus — squash a fixup: `jj squash`

🧩 The Undocumented StackUnsolved

📖 Story

You were coding fast and created three changes without descriptions. Your team uses a PR tool that reads jj descriptions to generate release notes. jj log shows three consecutive "(no description set)" entries. The files inside tell you what each change does — read them and describe each one accurately. Rules from your team's convention: - Must start with a verb (Add, Fix, Update, Remove, Refactor) - Must mention the file or feature changed - No "WIP" or vague messages

Goal

jj log -r 'all()' must:

not contain "(no description set)"

jj Terminal

🧩 Problem: The Undocumented Stack

Three changes landed with no descriptions. Name them all correctly before the PR review.

Use the terminal to solve the problem. jj log -r 'all()' will be checked automatically.