Clone this repo:
  1. b400c56 Generated files from "codesearch-gen-chromium-linux" build 824, revision 8555f372bec6701b15e143866d4c9a88970df336 by Automatic Generated Files Sync · 2 hours ago master
  2. b7e3a8d Generated files from "codesearch-gen-chromium-linux" build 823, revision 6323897a103b7f51983979498bae3018bf3d3b4e by Automatic Generated Files Sync · 6 hours ago
  3. a953e30 Generated files from "codesearch-gen-chromium-linux" build 821, revision bb2ecc3904828a1619cf7c55d66b2b19731782e8 by Automatic Generated Files Sync · 14 hours ago
  4. 8221d84 Generated files from "codesearch-gen-chromium-linux" build 820, revision aaa32d0ed6c515bd8e92c311a27d198b803369e6 by Automatic Generated Files Sync · 18 hours ago
  5. b242cc7 Generated files from "codesearch-gen-chromium-linux" build 819, revision a057906457c8e23ca26e98ac2b97740653a97d2f by Automatic Generated Files Sync · 22 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.