Update README.md with correct git cl format invocation.

Because we don't have clang format in the build tree, running
'git cl format' if proto files have been changed will error out. Passing
the --no-clang-format flag prevents that.

Change-Id: I437605474483df6e928293a7f3995e6283da699f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2352531
Auto-Submit: Garrett Beaty <gbeaty@chromium.org>
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
1 file changed
tree: ae7c8b2910b6fb50b3bad1fc470294d9c7c3677e
  1. infra/
  2. scripts/
  3. site_config/
  4. third_party/
  5. .gitattributes
  6. .gitignore
  7. .style.yapf
  8. .vpython
  9. .yapfignore
  10. codereview.settings
  11. CROS_OWNERS
  12. DEPS
  13. environment.cfg.py
  14. LICENSE
  15. OWNERS
  16. PRESUBMIT.py
  17. README.md
  18. WATCHLISTS
README.md

Recipes

If you're here to make a change to ‘recipes’ (the code located in scripts/slave/recipes*), please take a look at the README for more information pertaining to recipes.

Style

The preferred style is PEP8 with two-space indent; that is, the Chromium Python style. Functions use lowercase_with_underscores, with the exception of the special functions RunSteps and RunTests in recipes. Use yapf (git cl format --no-clang-format) to autoformat new code.