Clone this repo:
  1. 074a6ec Generated files from "codesearch-gen-chromium-android" build 8433, revision 74382593582f2e03c8cd26b27dcfaf523efdcffa by Automatic Generated Files Sync · 2 hours ago master
  2. 0d61117 Generated files from "codesearch-gen-chromium-lacros" build 546, revision 74382593582f2e03c8cd26b27dcfaf523efdcffa by Automatic Generated Files Sync · 3 hours ago
  3. 929bb8d Generated files from "codesearch-gen-chromium-chromiumos" build 9073, revision 90f07421faa9be7ca2570135ea98d4c8c5903695 by Automatic Generated Files Sync · 4 hours ago
  4. 0f221ed Generated files from "codesearch-gen-chromium-linux" build 9348, revision 90f07421faa9be7ca2570135ea98d4c8c5903695 by Automatic Generated Files Sync · 4 hours ago
  5. 7d9318b Generated files from "codesearch-gen-chromium-win" build 6452, revision 90f07421faa9be7ca2570135ea98d4c8c5903695 by Automatic Generated Files Sync · 4 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 (https://cs.chromium.org).

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.