Understanding the TODOs in your Codebase

#codequality #productivity

I've been working on a side project called tickgit, which is an experiment in code-based project management.

I put together a small UI which can present the TODOs in public github repos, see facebook/react for instance: https://todos.augmentable.dev/?repo=https://github.com/facebook/react

I'm wondering if this is a useful point-of-view into a codebase, as a way of summarizing items that need to get done. What do you think? Could you see it being useful for the codebases you work on?

I'm thinking about adding some search functionality and parsing out the age of TODOs as well, to have a sort order available...