Clone this repo:
  1. 3eb620d Generated files from "codesearch-gen-chromium-linux" build 303, revision d1c55391bd4f08ce3f5f57c4c6e7d3cb50ff6e51 by Automatic Generated Files Sync · 6 minutes ago master
  2. c1287df Generated files from "codesearch-gen-chromium-linux" build 302, revision c85bdf433f16428084e93da3b24bf5e86e0f117e by Automatic Generated Files Sync · 5 hours ago
  3. 85fe09d Generated files from "codesearch-gen-chromium-linux" build 301, revision 4e2b55c5fa7a354b3ae2f14e2f6d8201190a36a0 by Automatic Generated Files Sync · 8 hours ago
  4. a42c301 Generated files from "codesearch-gen-chromium-linux" build 300, revision eb6aa22b8590cadc206e4abcc5ad13c05d6ef695 by Automatic Generated Files Sync · 12 hours ago
  5. a7c5513 Generated files from "codesearch-gen-chromium-linux" build 299, revision a737f9c91cf432640a454d51ffca2d398ef00c00 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.