Clone this repo:

Branches

  1. 87dd729 Generated files from "codesearch-gen-chromium-android" build 8695538951599554113, revision bc39d1623c203110bb7e10e6ab5b05ae0851abef by Automatic Generated Files Sync · 8 minutes ago main
  2. 89827147 Generated files from "codesearch-gen-chromium-webview" build 8695538952711687713, revision bc39d1623c203110bb7e10e6ab5b05ae0851abef by Automatic Generated Files Sync · 47 minutes ago
  3. 971db5c Generated files from "codesearch-gen-chromium-ios" build 8695538952489435153, revision bc39d1623c203110bb7e10e6ab5b05ae0851abef by Automatic Generated Files Sync · 49 minutes ago
  4. b214e66 Generated files from "codesearch-gen-chromium-cronet" build 8695538951966961121, revision bc39d1623c203110bb7e10e6ab5b05ae0851abef by Automatic Generated Files Sync · 77 minutes ago
  5. cfd094c8 Generated files from "codesearch-gen-chromium-ios" build 8695543256450019601, revision bb0326a0180dd748ec40c252df3855dd0ea806bc 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.