commit | 6bef84f89e698e4bf3f9b7d15dc8b3b44adbb2e9 | [log] [tgz] |
---|---|---|
author | Nicolas Ouellet-Payeur <nicolaso@chromium.org> | Thu Jul 14 19:58:40 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jul 14 19:58:40 2022 |
tree | 884f867059cfd59db5c1c30aa6432b92dcabd274 | |
parent | ce7eeda269f61d4b7066430262887ebe99b9cc8d [diff] |
[Traffic Annotation] Supplement developer documentation An offline conversation revealed that the instructions on running auditor.py can be hard to find from just CQ output (which runs check_network_annotations.py). Add a comment in check_network_annotations.py telling contributors where they can find instructions on running auditor.py locally. Also, update the README to include the "fast" way to run the auditor (building the `traffic_annotation_proto` target rather than the `chrome` target). Change-Id: I214ea41ae45c58ce39b55f15dbaaa2ef839ee320 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3738258 Reviewed-by: Kenneth Russell <kbr@chromium.org> Commit-Queue: Nicolas Ouellet-Payeur <nicolaso@chromium.org> Reviewed-by: David Maunder <davidjm@chromium.org> Cr-Commit-Position: refs/heads/main@{#1024385}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.