Clone this repo:

Branches

  1. 0cabb89 Generated files from "codesearch-gen-chromium-cronet" build 8693062654196700129, revision 17f3722606b1972621e712ff70afb22cbb830a10 by Automatic Generated Files Sync · 4 minutes ago main
  2. a38b9cf010 Generated files from "codesearch-gen-chromium-ios" build 8693062654135966769, revision 17f3722606b1972621e712ff70afb22cbb830a10 by Automatic Generated Files Sync · 13 minutes ago
  3. 9acaec9 Generated files from "codesearch-gen-chromium-webview" build 8693062654375761329, revision 17f3722606b1972621e712ff70afb22cbb830a10 by Automatic Generated Files Sync · 14 minutes ago
  4. 01316235 Generated files from "codesearch-gen-chromium-android" build 8693077756490666337, revision b55aadeb7e2f9bf6526f58e1f2f9a8c3d01a37da by Automatic Generated Files Sync · 2 hours ago
  5. ed68e40 Generated files from "codesearch-gen-chromium-fuchsia" build 8693077754993861601, revision b55aadeb7e2f9bf6526f58e1f2f9a8c3d01a37da 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.