Clone this repo:

Branches

  1. f1ea0154 Generated files from "codesearch-gen-chromium-linux" build 8689827564742766689, revision 08b1299301bae9c48bfe9594ea0eb596f296f14b by Automatic Generated Files Sync · 6 minutes ago main
  2. b77b1e2 Generated files from "codesearch-gen-chromium-chromiumos" build 8689827563169731121, revision 08b1299301bae9c48bfe9594ea0eb596f296f14b by Automatic Generated Files Sync · 8 minutes ago
  3. c154807a Generated files from "codesearch-gen-chromium-ios" build 8689827563510830801, revision 08b1299301bae9c48bfe9594ea0eb596f296f14b by Automatic Generated Files Sync · 13 minutes ago
  4. 5c1804a Generated files from "codesearch-gen-chromium-webview" build 8689827563956864049, revision 08b1299301bae9c48bfe9594ea0eb596f296f14b by Automatic Generated Files Sync · 34 minutes ago
  5. aa5b914 Generated files from "codesearch-gen-chromium-cronet" build 8689827563855512465, revision 08b1299301bae9c48bfe9594ea0eb596f296f14b by Automatic Generated Files Sync · 47 minutes 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.