Clone this repo:

Branches

  1. d20eab0 Generated files from "codesearch-gen-chromium-chromiumos" build 8715364611914533105, revision 3f2edd906f65c0580c3af0b4a868439575465859 by Automatic Generated Files Sync · 11 minutes ago main
  2. f9305e10 Generated files from "codesearch-gen-chromium-android" build 8715364610377181889, revision 3f2edd906f65c0580c3af0b4a868439575465859 by Automatic Generated Files Sync · 15 minutes ago
  3. 25683ebef Generated files from "codesearch-gen-chromium-linux" build 8715364611493406241, revision 3f2edd906f65c0580c3af0b4a868439575465859 by Automatic Generated Files Sync · 36 minutes ago
  4. ab74fd8 Generated files from "codesearch-gen-chromium-mac" build 8715364610456380849, revision 3f2edd906f65c0580c3af0b4a868439575465859 by Automatic Generated Files Sync · 41 minutes ago
  5. 346e4e7 Generated files from "codesearch-gen-chromium-fuchsia" build 8715364611348482193, revision 3f2edd906f65c0580c3af0b4a868439575465859 by Automatic Generated Files Sync · 60 minutes 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 Codeserach builder (e.g. codesearch-gen-chromium-linux) regularly does a full build of Chromium, and afterwards pushes all the generated files (from the src/out/{out_dir}/gen directory) into this git 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.