<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/todos-jj-style-d9ahy7oua" -->

---
title: TODOs JJ Style | daily.dev
description: Empty commits in JJ (Jujutsu) can replace a TODO.md file for tracking tasks. The author writes empty changes with descriptions for planned work, then rebases...
canonical: https://daily.dev/posts/todos-jj-style-d9ahy7oua
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: TODOs JJ Style | daily.dev
og:description: Empty commits in JJ (Jujutsu) can replace a TODO.md file for tracking tasks. The author writes empty changes with descriptions for planned work, then rebases...
og:url: https://daily.dev/posts/todos-jj-style-d9ahy7oua
og:image: https://api.daily.dev/og/posts/D9AhY7ouA.png
og:image:alt: TODOs JJ Style
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# TODOs JJ Style

**[Lobsters](https://daily.dev/sources/lobsters)** · 2 min read · 0 upvotes · 0 comments

## Summary

Empty commits in JJ (Jujutsu) can replace a TODO.md file for tracking tasks. The author writes empty changes with descriptions for planned work, then rebases one out of the 'TODO tree' onto another change when ready to start it. Since the commits are empty, rebasing them forward never causes conflicts. Dependent TODOs stack as empty commits on top of other empty commits. Setting git.private-commits to description('private:*') keeps commits prefixed 'private:' from being pushed.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://bwc9876.dev/blog/jj_todo>

## Questions this post answers

### How can I track TODOs directly in Jujutsu (JJ) instead of a TODO.md file?

Create empty changes in JJ with descriptions of planned work, forming a 'TODO tree' of commits with no file changes. When ready to start a task, rebase that empty commit out of the tree onto the change where the work will happen. Because the commits are empty, rebasing them forward as other work lands never causes conflicts, and dependent TODOs can be stacked as empty commits on top of each other.

_Developers building a JJ-based workflow can compare version control tricks like this on daily.dev._

### How do I keep certain Jujutsu commits from being pushed to a shared remote?

Configure the git.private-commits setting to match a description prefix, for example description('private:*'), so any commit whose description starts with 'private:' is excluded from pushes. In Home Manager this is set via programs.jujutsu.settings.git.private-commits. This keeps local-only commits, like personal TODOs, from leaking into the remote repository.

_Anyone tuning JJ or git configs to avoid leaking local commits can find similar setups on daily.dev._

## Community take

How the wider developer community reacted, aggregated from 2 discussions and 9 comments across hackernews, lobsters (as of 2026-11-22).

**TL;DR:** Developers find the empty-commit TODO tree clever and worth adopting, though a few note it can get messy at scale and share their own tweaks or alternative workflows.

**Sentiment:** 65% positive · 30% mixed · 5% skeptical

**The case for**

- Writing the commit description doubles as writing the TODO, saving a step.
- Keeps the TODO item tied to the point in history where it was conceived.
- Can be combined with custom log templates to surface TODO-prefixed commits nicely.
- People are already adopting WIP-style commits and see this as a natural extension.

**The pushback**

- Keeping a growing tree of empty commits organized can become messy over time.
- One person reverted to a TODO.md file kept in its own commit instead.

**By community**

- hackernews (mixed): No substantive discussion present.
- lobsters (positive): Mostly enthusiastic about the approach, with a couple of practical tweaks and one admission that it can get unwieldy.

**Open questions**

- How to keep the empty-commit TODO tree organized as it grows larger.

**Highlights**

> Even if it doesn't feel very groundbreaking, this is the kind of thing that you could just never think about coming from the "message last" way of git thinking. I've been doing a lot more "WIP" commits with small ideas, but never took it to the point of an empty commit, will be adopting this.
> — [ejri on lobsters · 9 points](https://lobste.rs/s/qxzs4y/todos_jj_style#c_o8v3dj)

> I think a tree like this is interesting especially for creating hierarchies of tasks but I would struggle keeping the empty commits organized. In my default log template I made it so if a commit starts with "wip" and contains "todo:" then it shows the whole description. This way when I spam `jj log` in a repo I get hit with my todo list/message. ```toml template-aliases."show_desc(desc)" = ''' if(   desc.starts_with("wip") && desc.lower().contains("todo:"),   label("todo", desc.lines().skip(1).join("\n")),   "" ) ''' ``` which results in this: ``` ○  yxlrqxpu me wip (empty) 31 seconds ago │  todo: ~  - [ ] task 1    - [ ] task 2 ```
> — [daylin on lobsters · 4 points](https://lobste.rs/s/qxzs4y/todos_jj_style#c_glrgeo)

> I tried doing something like this, but after a while it just becomes messy(yes, it's a skill issue), so I reverted back to using TODO.md, but I keep that file in it's own separate commit, and add that commit to my currently worked on megamerge
> — [olex on lobsters · 6 points, 1 comments](https://lobste.rs/s/qxzs4y/todos_jj_style#c_99kium)

> Seems smart - you are gonna write those descriptions anyway so saves a step.
> — [jedahan on lobsters · 3 points](https://lobste.rs/s/qxzs4y/todos_jj_style#c_pixnue)

**Source threads**

- [hackernews](https://news.ycombinator.com/item?id=50594083) · 2 points · 0 comments
- [lobsters](https://lobste.rs/s/qxzs4y/todos_jj_style) · 51 points · 9 comments

## Similar posts on daily.dev

- [Reviewing large changes with Jujutsu](https://daily.dev/posts/reviewing-large-changes-with-jujutsu-ocxv3pmjs) · Lobsters · 2 upvotes · 1 comments
- [Jujutsu \(JJ\): An Alternative to Git? Jujutsu proposes to be simpler yet more powerful than Git. But is it worth switching? Let's find out.](https://daily.dev/posts/jujutsu-jj-an-alternative-to-git-jujutsu-proposes-to-be-simpler-yet-more-powerful-than-git-but--qycicuerv) · The Miners · 78 upvotes · 15 comments
- [How I use Jujutsu](https://daily.dev/posts/how-i-use-jujutsu-pu0cj8npp) · Lobsters · 42 upvotes · 0 comments
- [Jujutsu VCS 101](https://daily.dev/posts/jujutsu-vcs-101-t8fi750ib) · Viget · 27 upvotes · 5 comments
- [defeating git rigour fatigue with jujutsu](https://daily.dev/posts/defeating-git-rigour-fatigue-with-jujutsu-ogmh4nllz) · Hacker News · 5 upvotes · 0 comments

---

Tags: [#git](https://daily.dev/tags/git), [#version-control](https://daily.dev/tags/version-control)

[View this post on daily.dev](https://daily.dev/posts/todos-jj-style-d9ahy7oua)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"TODOs JJ Style","url":"https://daily.dev/posts/todos-jj-style-d9ahy7oua","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/todos-jj-style-d9ahy7oua"},"datePublished":"2026-11-22T08:49:38.400Z","dateModified":"2026-11-22T08:50:38.334Z","description":"Empty commits in JJ (Jujutsu) can replace a TODO.md file for tracking tasks. The author writes empty changes with descriptions for planned work, then rebases...","image":"https://media.daily.dev/image/upload/s--HRgLpUt6--/f_auto/v1722860399/public/Placeholder%2003","thumbnailUrl":"https://media.daily.dev/image/upload/s--HRgLpUt6--/f_auto/v1722860399/public/Placeholder%2003","isAccessibleForFree":true,"articleSection":"Lobsters","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Lobsters","logo":"https://media.daily.dev/image/upload/s--tl8v_Fku--/f_auto,t_logo/v1698841318/logos/lobste.jpg","url":"https://daily.dev/sources/lobsters"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/todos-jj-style-d9ahy7oua","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"git,version-control","timeRequired":"PT2M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Lobsters","item":"https://daily.dev/sources/lobsters"},{"@type":"ListItem","position":3,"name":"TODOs JJ Style"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/todos-jj-style-d9ahy7oua#faq","mainEntity":[{"@type":"Question","name":"How can I track TODOs directly in Jujutsu (JJ) instead of a TODO.md file?","acceptedAnswer":{"@type":"Answer","text":"Create empty changes in JJ with descriptions of planned work, forming a 'TODO tree' of commits with no file changes. When ready to start a task, rebase that empty commit out of the tree onto the change where the work will happen. Because the commits are empty, rebasing them forward as other work lands never causes conflicts, and dependent TODOs can be stacked as empty commits on top of each other. Developers building a JJ-based workflow can compare version control tricks like this on daily.dev."}},{"@type":"Question","name":"How do I keep certain Jujutsu commits from being pushed to a shared remote?","acceptedAnswer":{"@type":"Answer","text":"Configure the git.private-commits setting to match a description prefix, for example description('private:*'), so any commit whose description starts with 'private:' is excluded from pushes. In Home Manager this is set via programs.jujutsu.settings.git.private-commits. This keeps local-only commits, like personal TODOs, from leaking into the remote repository. Anyone tuning JJ or git configs to avoid leaking local commits can find similar setups on daily.dev."}}]}
```

