Clone this repo:

Branches

  1. 07d68509 Generated files from "codesearch-gen-chromium-chromiumos" build 8710125053755580289, revision 20f8638dabed873cbb3ef802adb44767dca19751 by Automatic Generated Files Sync · 32 minutes ago main
  2. 33ec300 Generated files from "codesearch-gen-chromium-win" build 8710125052307730897, revision 20f8638dabed873cbb3ef802adb44767dca19751 by Automatic Generated Files Sync · 34 minutes ago
  3. d1b17a64 Generated files from "codesearch-gen-chromium-fuchsia" build 8710125052261468193, revision 20f8638dabed873cbb3ef802adb44767dca19751 by Automatic Generated Files Sync · 38 minutes ago
  4. 4e52cfc Generated files from "codesearch-gen-chromium-linux" build 8710125052569221265, revision 20f8638dabed873cbb3ef802adb44767dca19751 by Automatic Generated Files Sync · 62 minutes ago
  5. 99affbb Generated files from "codesearch-gen-chromium-mac" build 8710125052437998049, revision 20f8638dabed873cbb3ef802adb44767dca19751 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.