Clone this repo:

Branches

  1. be2d3155 Generated files from "codesearch-gen-chromium-cronet" build 8701473035229334033, revision 934eb1d8ee59041ed425a4e4d843f015789c5a95 by Automatic Generated Files Sync · 40 minutes ago main
  2. e1b54179 Generated files from "codesearch-gen-chromium-ios" build 8701488150076860465, revision b6cf2846f815e220e0bca95894aa92177af24263 by Automatic Generated Files Sync · 2 hours ago
  3. 353f616 Generated files from "codesearch-gen-chromium-android" build 8701488150242375217, revision b6cf2846f815e220e0bca95894aa92177af24263 by Automatic Generated Files Sync · 3 hours ago
  4. afca4ab Generated files from "codesearch-gen-chromium-win" build 8701488151222610417, revision b6cf2846f815e220e0bca95894aa92177af24263 by Automatic Generated Files Sync · 3 hours ago
  5. 3c40fdc Generated files from "codesearch-gen-chromium-mac" build 8701488150523947265, revision b6cf2846f815e220e0bca95894aa92177af24263 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.