Clone this repo:

Branches

  1. a016d67e Generated files from "codesearch-gen-chromium-cronet" build 8708856728399087521, revision 3fecd97ad03e1a4801663e7247abba8a223420fa by Automatic Generated Files Sync · 16 minutes ago main
  2. 73fe971 Generated files from "codesearch-gen-chromium-win" build 8708871805227613937, revision e60dd28ed8b38c696f54b3ef450126710569debd by Automatic Generated Files Sync · 3 hours ago
  3. 4faae06 Generated files from "codesearch-gen-chromium-chromiumos" build 8708871805974091505, revision e60dd28ed8b38c696f54b3ef450126710569debd by Automatic Generated Files Sync · 3 hours ago
  4. d27e6392 Generated files from "codesearch-gen-chromium-linux" build 8708871804943955185, revision e60dd28ed8b38c696f54b3ef450126710569debd by Automatic Generated Files Sync · 3 hours ago
  5. c7b6e9f Generated files from "codesearch-gen-chromium-android" build 8708871806198707793, revision e60dd28ed8b38c696f54b3ef450126710569debd 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.