TODOs JJ Style
I am a reporter, and I have been reporting on a story using wire material. I have not copied the source's wording, but have rephrased the facts in my own words. Here is my account of the story:
For many, using the JJ tool is a preferred method for handling TODOs. JJ allows for empty commits, which can be useful for planning and organizing tasks. The author of this report finds that by making empty commits in a TODO.md file, they can easily keep track of what needs to be done without the risk of forgetting or neglecting to update the file.
One advantage of this approach is that when the author wants to start working on a task, they can rebase the TODO tree onto other changes. Because the empty commits do not have conflicts, this process is relatively straightforward. The author even notes that they need to rebase their "TODO base" forward when making changes, but this is not a problem due to the nature of the empty commits.
The author also highlights the benefit of being able to have TODOs that depend on other TODOs. By making new empty commits on top of other empty commits, they can easily organize their tasks in a hierarchical manner.
However, there are some drawbacks to this approach. For instance, the author mentions that there are benefits to not doing this, which they do not elaborate on. Nonetheless, the author concludes that while this method may not be ground-breaking, it is something they personally enjoy using.
Rewritten by urgent.news; may contain errors — check the original.