Clone this repo:

Branches

  1. c11ab1f1 Generated files from "codesearch-gen-chromium-mac" build 8689714290298903281, revision 771b866fce3033a0a187194c4e6f4ddffe4ec15c by Automatic Generated Files Sync · 2 hours ago main
  2. e2c7d9a Generated files from "codesearch-gen-chromium-win" build 8689714290893471281, revision 771b866fce3033a0a187194c4e6f4ddffe4ec15c by Automatic Generated Files Sync · 2 hours ago
  3. 449720d Generated files from "codesearch-gen-chromium-android" build 8689714290442357233, revision 771b866fce3033a0a187194c4e6f4ddffe4ec15c by Automatic Generated Files Sync · 2 hours ago
  4. 6effaba Generated files from "codesearch-gen-chromium-chromiumos" build 8689714290599009889, revision 771b866fce3033a0a187194c4e6f4ddffe4ec15c by Automatic Generated Files Sync · 3 hours ago
  5. 4830f22 Generated files from "codesearch-gen-chromium-fuchsia" build 8689714289762631873, revision 771b866fce3033a0a187194c4e6f4ddffe4ec15c 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.