How tooling can help stay on top of the never-ending cycle of dependency updates for projects hosted on GitHub.

Thanks!

So, you’re proposing adding a third state (“done”) to tasks (as an addition to “active” and “archived”). It should be doable; I’ll see if I can add it as optional behavior via a configuration parameter.

Yes, that would be slick. Then in that mode return would toggle between active and done.

Having a command to archive all done tasks would make it easy to remove the clutter.

Thanks for considering this.

That’s a nice way to put it :)

Thanks!

@bachmeier Yeah, you can get a lot of utility out of combining tools like fzf, gum together in a shell script.

For more fine grained controls, you can look into TUI frameworks like bubbletea, ratatui, Textual etc.

Haha, I didn’t think too deep about the choice of the tasks before putting them in, but you’re on to something here.

I tried to design omm to overcome that futility, at least for myself. Having said that, I find it funny that I might’ve subconsciously remarked on it in the demo.