Clone this repo:

Branches

  1. a649cea Generated files from "codesearch-gen-chromium-mac" build 8684233188433172321, revision 1c547939cbb7e415491054e55b118dbf5e40cd85 by Automatic Generated Files Sync · 2 hours ago main
  2. e8ad560 Generated files from "codesearch-gen-chromium-win" build 8684233188433172289, revision 1c547939cbb7e415491054e55b118dbf5e40cd85 by Automatic Generated Files Sync · 2 hours ago
  3. 3230afd Generated files from "codesearch-gen-chromium-chromiumos" build 8684233188433172401, revision 1c547939cbb7e415491054e55b118dbf5e40cd85 by Automatic Generated Files Sync · 3 hours ago
  4. f45cf4dd Generated files from "codesearch-gen-chromium-linux" build 8684233188433172337, revision 1c547939cbb7e415491054e55b118dbf5e40cd85 by Automatic Generated Files Sync · 3 hours ago
  5. 159be63 Generated files from "codesearch-gen-chromium-ios" build 8684233188433172353, revision 1c547939cbb7e415491054e55b118dbf5e40cd85 by Automatic Generated Files Sync · 3 hours ago

What's this?

This git repository exists to allow the source files generated during a Chromium build to be indexed by code search.

You do not need to clone this repository, and it is not used in any way during a build.

How does it work?

A Codeserach builder (e.g. codesearch-gen-chromium-linux) regularly does a full build of Chromium, and afterwards pushes all the generated files (from the src/out/{out_dir}/gen directory) into this git repository.

The code search crawler indexes that gitlink repository following all the gitlinks inside, which eventually leads it here and allows it to index the generated code.