Clone this repo:

Branches

  1. ddb77df Generated files from "codesearch-gen-chromium-win" build 8714669995350210801, revision 3830e671749ac214737c8d15c5d85acd389a4837 by Automatic Generated Files Sync · 11 minutes ago main
  2. 2cffd72 Generated files from "codesearch-gen-chromium-chromiumos" build 8714669995228088417, revision 3830e671749ac214737c8d15c5d85acd389a4837 by Automatic Generated Files Sync · 22 minutes ago
  3. 7f3dc1f Generated files from "codesearch-gen-chromium-android" build 8714669994881211425, revision 3830e671749ac214737c8d15c5d85acd389a4837 by Automatic Generated Files Sync · 35 minutes ago
  4. d991ad6 Generated files from "codesearch-gen-chromium-linux" build 8714669995808125617, revision 3830e671749ac214737c8d15c5d85acd389a4837 by Automatic Generated Files Sync · 60 minutes ago
  5. 8578d3ac Generated files from "codesearch-gen-chromium-mac" build 8714669994756134929, revision 3830e671749ac214737c8d15c5d85acd389a4837 by Automatic Generated Files Sync · 67 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.