Clone this repo:
  1. c63bbc1 Generated files from "codesearch-gen-chromium-win" build 7501, revision 492c83d6197b0ec873c68322e63622747f819273 by Automatic Generated Files Sync · 31 minutes ago master
  2. db38226 Generated files from "codesearch-gen-chromium-chromiumos" build 10160, revision 492c83d6197b0ec873c68322e63622747f819273 by Automatic Generated Files Sync · 2 hours ago
  3. 0681c52 Generated files from "codesearch-gen-chromium-linux" build 10443, revision 492c83d6197b0ec873c68322e63622747f819273 by Automatic Generated Files Sync · 2 hours ago
  4. 13b1421f Generated files from "codesearch-gen-chromium-android" build 9521, revision 492c83d6197b0ec873c68322e63622747f819273 by Automatic Generated Files Sync · 2 hours ago
  5. f578ab8 Generated files from "codesearch-gen-chromium-lacros" build 1643, revision 492c83d6197b0ec873c68322e63622747f819273 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.