> Put it in your git commit message. Yes, that's fine. Developers can also put TODOs in their git commit message. > Most commits people make are rather bad. I

> Put it in your git commit message. Yes, that's fine. Developers can also put TODOs in their git commit message. > Most commits people make are rather bad. Instead of taking us back to the stone age with TODOs, why not encourage better tool usage? I have a tool which fails if it finds a TODO in a comment without a Jira link on the same line. Since it fails if it finds such things, it's great for CI/CD piplines to block PRs until all of the oddball ends have been tied up and made visible to the product team. Alas, if we could get the product team to prioritize those TODOs then they can start to be removed from the codebase...