Clone this repo:
  1. f0566e5 Generated files from "codesearch-gen-chromium-chromiumos" build 5227, revision fb433e43903dcd7e2392607b39272ac559425130 by Automatic Generated Files Sync · 36 minutes ago master
  2. 2d8a8c2 Generated files from "codesearch-gen-chromium-linux" build 5421, revision fb433e43903dcd7e2392607b39272ac559425130 by Automatic Generated Files Sync · 50 minutes ago
  3. de131b5 Generated files from "codesearch-gen-chromium-android" build 4319, revision fb433e43903dcd7e2392607b39272ac559425130 by Automatic Generated Files Sync · 55 minutes ago
  4. e74968a Generated files from "codesearch-gen-chromium-win" build 3157, revision 49a0361397a985199107df0e5f01251adf057aaf by Automatic Generated Files Sync · 75 minutes ago
  5. 5fd145c Generated files from "codesearch-gen-chromium-chromiumos" build 5226, revision 49a0361397a985199107df0e5f01251adf057aaf 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 (https://cs.chromium.org).

You do not need to clone this repository, and it is not used in any way during a build.

How does it work?

A build slave regularly does a full Linux build of Chromium, and afterwards pushes all the generated files (from the src/out/Debug/gen directory) into this git repository.

Another build slave maintains a git repository containing gitlinks (git submodules) representing the dependencies specified in Chromium's DEPS file. That script also adds a gitlink named “out” pointing to this 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.