0

Revert "Make TODO style more explicit in the Chromium style guide"

This reverts commit d82b399572.

Reason for revert: Needs more discussion

Original change's description:
> Make TODO style more explicit in the Chromium style guide
>
> Change-Id: Ia9ae70da8ec056f271630803fe7cfa5751a24129
> Reference: go/crbug-todo-migration
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5598198
> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
> Commit-Queue: Alison Gale <agale@chromium.org>
> Reviewed-by: Rick Byers <rbyers@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1314069}

Change-Id: I94973e4b0715dd3b2130ce77f513920521b92cbd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5659428
Reviewed-by: Rick Byers <rbyers@chromium.org>
Auto-Submit: Alison Gale <agale@chromium.org>
Commit-Queue: Alison Gale <agale@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1321143}
This commit is contained in:
Alison Gale
2024-06-28 19:47:48 +00:00
committed by Chromium LUCI CQ
parent e25c8d0d31
commit 3701577c1e
4 changed files with 3 additions and 14 deletions

@ -315,7 +315,9 @@ Values of `Integer` type are also supported, which allows using a sentinel
### TODOs
See the language agnostic [TODO guidance](../todos.md).
* TODO should follow chromium convention. Examples:
* `TODO(username): Some sentence here.`
* `TODO(crbug.com/40192027): Even better to use a bug for context.`
### Parameter Comments