Clone this repo:

Branches

  1. 618326d3 Generated files from "codesearch-gen-chromium-win" build 8683660846894511985, revision 4850635c95ef1c5d863ea9db3bf9c78d1878e0e3 by Automatic Generated Files Sync · 47 minutes ago main
  2. 98a60f2 Generated files from "codesearch-gen-chromium-mac" build 8683660846894512017, revision 4850635c95ef1c5d863ea9db3bf9c78d1878e0e3 by Automatic Generated Files Sync · 71 minutes ago
  3. fc1cd65d Generated files from "codesearch-gen-chromium-ios" build 8683660846894512049, revision 4850635c95ef1c5d863ea9db3bf9c78d1878e0e3 by Automatic Generated Files Sync · 77 minutes ago
  4. d16a060 Generated files from "codesearch-gen-chromium-chromiumos" build 8683660846894512097, revision 4850635c95ef1c5d863ea9db3bf9c78d1878e0e3 by Automatic Generated Files Sync · 83 minutes ago
  5. 473e9bf Generated files from "codesearch-gen-chromium-linux" build 8683660846894512033, revision 4850635c95ef1c5d863ea9db3bf9c78d1878e0e3 by Automatic Generated Files Sync · 2 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 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.