If the TODO has a bug number, like TODO(#1301): add TODO bot, I think it makes sense to block a closing PR when the TODO is still there?

@tmatsuo perhaps we could add a convention like TODO(tmatsuo): add todo bot Refs: #939?

That way we still get user assignment.

@bcoe That works for me. @coryan WDYT?

I do not think developer names attached to TODOs make sense. What happens when they leave? What happens if somebody else wants to work on it?

In C++ the Google style guide requires 80 columns. Horizontal space is at a premium, // TODO(person): ... refs: #.... steals too much of it.

My $0.02: it should always be // TODO(#number) - action to take here

That's a good point. Referring to a github issue is more robust than assigning a member. We can assign members to that issue.

Previously, this was infeasible if we rely on the GitHub code search API (rate limits). Now, with Cloud Run, we can shallow clone the code and use grep to search for TODO entries.

Additionally, the bot could lint TODO comments