Clone this repo:
  1. 973c8d7 Generated files from "codesearch-gen-chromium-linux" build 1542, revision 78e1cc855a8e7d3289e4ca0cc3b698d5ff954e26 by Automatic Generated Files Sync · 17 minutes ago master
  2. 29d1570 Generated files from "codesearch-gen-chromium-linux" build 1541, revision 6b56ef714768608375710f5b0d5f7a9519cdf265 by Automatic Generated Files Sync · 4 hours ago
  3. 27dd985 Generated files from "codesearch-gen-chromium-linux" build 1540, revision 01dec7d4e645fc8a6673d6c7fc7c9735fa10aac9 by Automatic Generated Files Sync · 8 hours ago
  4. 2777f45 Generated files from "codesearch-gen-chromium-linux" build 1539, revision 9a51563bd22a3c1c015f48ad50e2e77c28516063 by Automatic Generated Files Sync · 12 hours ago
  5. 0263b27 Generated files from "codesearch-gen-chromium-linux" build 1538, revision 2c0161cf8b88ce48dd9038327be9a362feb0c018 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.