Clone this repo:
  1. e89192a Generated files from "codesearch-gen-chromium-linux" build 2299, revision efb6eca4dfa14ea18a449c2f0c3c659dd1d5ce01 by Automatic Generated Files Sync · 14 minutes ago master
  2. 27f34f8 Generated files from "codesearch-gen-chromium-linux" build 2298, revision 35b3464dccd14d07d154bd660adc9a608ed5bd5c by Automatic Generated Files Sync · 4 hours ago
  3. 6984cff Generated files from "codesearch-gen-chromium-linux" build 2297, revision 555aac2d836e74924d46159dd24532b65e89b6b3 by Automatic Generated Files Sync · 8 hours ago
  4. 4b68e40 Generated files from "codesearch-gen-chromium-linux" build 2296, revision 12522853769d394073efa4531964a6addef6698a by Automatic Generated Files Sync · 12 hours ago
  5. d248c95 Generated files from "codesearch-gen-chromium-linux" build 2295, revision b07aa40400f4d91bcbafabd01bfc5b77e477a34b 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.