Clone this repo:

Branches

  1. 19b6a129 Generated files from "codesearch-gen-chromium-ios" build 8680352675773281409, revision 0348b4ba252699680d0c3b6ab61f5683a0169e35 by Automatic Generated Files Sync · 3 hours ago main
  2. b66c31b Generated files from "codesearch-gen-chromium-win" build 8680352675773281345, revision 0348b4ba252699680d0c3b6ab61f5683a0169e35 by Automatic Generated Files Sync · 3 hours ago
  3. 2cb67bd8 Generated files from "codesearch-gen-chromium-android" build 8680352675773281473, revision 0348b4ba252699680d0c3b6ab61f5683a0169e35 by Automatic Generated Files Sync · 3 hours ago
  4. d3f80e53 Generated files from "codesearch-gen-chromium-mac" build 8680352675773281377, revision 0348b4ba252699680d0c3b6ab61f5683a0169e35 by Automatic Generated Files Sync · 3 hours ago
  5. 3ee6e61 Generated files from "codesearch-gen-chromium-fuchsia" build 8680352675773281425, revision 0348b4ba252699680d0c3b6ab61f5683a0169e35 by Automatic Generated Files Sync · 3 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.