Clone this repo:

Branches

  1. ea88f4f Generated files from "codesearch-gen-chromium-win" build 8684097332059477569, revision 2dd72a651c5d32567c8e4e25ca990ff2e6ba867f by Automatic Generated Files Sync · 2 hours ago main
  2. 720e988 Generated files from "codesearch-gen-chromium-ios" build 8684097332059477633, revision 2dd72a651c5d32567c8e4e25ca990ff2e6ba867f by Automatic Generated Files Sync · 3 hours ago
  3. 0812694 Generated files from "codesearch-gen-chromium-mac" build 8684097332059477601, revision 2dd72a651c5d32567c8e4e25ca990ff2e6ba867f by Automatic Generated Files Sync · 3 hours ago
  4. 2e89339 Generated files from "codesearch-gen-chromium-android" build 8684097332059477697, revision 2dd72a651c5d32567c8e4e25ca990ff2e6ba867f by Automatic Generated Files Sync · 3 hours ago
  5. 170d1fd Generated files from "codesearch-gen-chromium-chromiumos" build 8684097332059477681, revision 2dd72a651c5d32567c8e4e25ca990ff2e6ba867f 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.