Clone this repo:
  1. 0068627 Generated files from "codesearch-gen-chromium-linux" build 2662, revision 57064b0b5148b8ba131c7bf1fe1b8ca7aee59d87 by Automatic Generated Files Sync · 33 minutes ago master
  2. 0735652 Generated files from "codesearch-gen-chromium-linux" build 2661, revision d48e4a5027d99df10556c28382948c31f419e815 by Automatic Generated Files Sync · 4 hours ago
  3. 1da3568 Generated files from "codesearch-gen-chromium-linux" build 2660, revision dc67d9552653ab8f23463facf28b9154e70fd39d by Automatic Generated Files Sync · 9 hours ago
  4. 780f044 Generated files from "codesearch-gen-chromium-linux" build 2659, revision 2f66db425ca30a4f58d0a2ac4e7e03f36f1e2dd0 by Automatic Generated Files Sync · 12 hours ago
  5. c0edadc Generated files from "codesearch-gen-chromium-linux" build 2658, revision 43d41bed21f1cfe2a059d6d754ad5dbceb4b6d97 by Automatic Generated Files Sync · 16 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.