Clone this repo:
  1. a2333e0 Generated files from "codesearch-gen-chromium-linux" build 526, revision 61472254f109375173180671106927aa6867699a by Automatic Generated Files Sync · 15 minutes ago master
  2. 6233b27 Generated files from "codesearch-gen-chromium-linux" build 525, revision d6278fe9c587f7af6d7d26ee34cbdfc4b69d0d64 by Automatic Generated Files Sync · 4 hours ago
  3. 616c7c9 Generated files from "codesearch-gen-chromium-linux" build 524, revision 8354c1c180c052a5153e5ac65ccb2bb628120bee by Automatic Generated Files Sync · 8 hours ago
  4. 78ef267 Generated files from "codesearch-gen-chromium-linux" build 523, revision b96dfa5b9c0656cc9a8dc0e67f1ab3b547c45a84 by Automatic Generated Files Sync · 10 hours ago
  5. 05a4086 Generated files from "codesearch-gen-chromium-linux" build 522, revision 55045d24790784642f0ced778c3a1b0e65ca21e8 by Automatic Generated Files Sync · 13 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.