Skip to content

Commit

Permalink
Auto-format files.
Browse files Browse the repository at this point in the history 
PiperOrigin-RevId: 314165682
  • Loading branch information
@code-health-devguide-copybara @copybara-github
code-health-devguide-copybara authored and copybara-github committed Jun 1, 2020
1 parent e90d7f2 commit 663400b
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions review/developer/cl-descriptions.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -27,8 +27,8 @@ whole description to understand what your CL actually *did* or how it differs
from other CLs. That is, the first line should stand alone, allowing readers to
skim through code history much faster.

Try to keep your first line short, focused, and to the point.
The clarity and utility to the reader should be the top concern.
Try to keep your first line short, focused, and to the point. The clarity and
utility to the reader should be the top concern.

By tradition, the first line of a CL description is a complete sentence, written
as though it were an order (an imperative sentence). For example, say
Expand Down

0 comments on commit 663400b

Please sign in to comment.