@lig that looks neat!
this post was submitted on 10 Jan 2025
55 points (96.6% liked)
Git
2960 readers
1 users here now
Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
Resources
Rules
- Follow programming.dev rules
- Be excellent to each other, no hostility towards users for any reason
- No spam of tools/companies/advertisements. Itβs OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.
Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.
founded 2 years ago
MODERATORS
But when I put @todo in my code, the point is to never revisit it. I don't want to be reminded every time I open the repo!
This one isn't for you then :)
Haha, nice work on it tho.
That's actually pretty neat
excellent! i can now remove my eternal TODO to write this myself :D
You're welcome:)
Maybe you want to scan for FIXME: too?
That could be an option. Care to fill an issue?:)
https://codeberg.org/lig/todo-md/issues/4
I didn't create one because I won't be using the project, but suggested it here for your consideration. :)
Outside of work-in-progress or exploration branches, I don't commit or merge TODOs. Typically, I consider them merge/land blockers. Because most of the time, they're never resolved. And in that case, I much prefer documentation and statements; reasoning of why it is the way it is, or opportunities.
In projects I work on we use NOCOMMIT for these blockers and they'll fail the build. It's honestly lovely to have something to leave yourself a note that the build catches for you.
a TODO can often be expressed in a throw NotImplementedError or similar, but a comment is where danger lies
Neat!