Clone this repo:
  1. e4f3f84 Generated files from "codesearch-gen-chromium-linux" build 1144, revision 38b2fad16c23a6ce94509a76c249230ad6623c17 by Automatic Generated Files Sync · 4 hours ago master
  2. a4f93f2 Generated files from "codesearch-gen-chromium-linux" build 1143, revision 95bab29803f610d9e3cb14abe4e6e81086dcbc8e by Automatic Generated Files Sync · 8 hours ago
  3. e93b4ec Generated files from "codesearch-gen-chromium-linux" build 1142, revision c2501b459b6f4ee75b89846b0d0dc0f1b918135e by Automatic Generated Files Sync · 11 hours ago
  4. 8e2830a Generated files from "codesearch-gen-chromium-linux" build 1141, revision 2c792cfa50fb6e6ab02185ce846076ac8885bdb2 by Automatic Generated Files Sync · 15 hours ago
  5. e6f1a44 Generated files from "codesearch-gen-chromium-linux" build 1140, revision 63c4dc41d2b90dc3386e331b62ee893a32bb0b11 by Automatic Generated Files Sync · 20 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 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.