Clone this repo:

Branches

  1. f8239878 Generated files from "codesearch-gen-chromium-webview" build 8697335813707905777, revision 47cc24b3abb9ae205e7f4513d7b530265de64067 by Automatic Generated Files Sync · 49 minutes ago main
  2. e4edb9e Generated files from "codesearch-gen-chromium-ios" build 8697335813698259057, revision 47cc24b3abb9ae205e7f4513d7b530265de64067 by Automatic Generated Files Sync · 55 minutes ago
  3. 6daa595 Generated files from "codesearch-gen-chromium-cronet" build 8697335813961528481, revision 47cc24b3abb9ae205e7f4513d7b530265de64067 by Automatic Generated Files Sync · 85 minutes ago
  4. 042da8f Generated files from "codesearch-gen-chromium-chromiumos" build 8697350885474454513, revision dbbc0800dd756619d26c0c5836d8af556b7a7719 by Automatic Generated Files Sync · 4 hours ago
  5. 0ddb3739 Generated files from "codesearch-gen-chromium-fuchsia" build 8697350883967898417, revision dbbc0800dd756619d26c0c5836d8af556b7a7719 by Automatic Generated Files Sync · 4 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.