Clone this repo:

Branches

  1. a360bff3 Generated files from "codesearch-gen-chromium-webview" build 8694542375782391473, revision 188691d01b1ae989c8a005d75694f1bb90ad9121 by Automatic Generated Files Sync · 39 minutes ago main
  2. d3c0ba34 Generated files from "codesearch-gen-chromium-ios" build 8694542374951967873, revision 188691d01b1ae989c8a005d75694f1bb90ad9121 by Automatic Generated Files Sync · 41 minutes ago
  3. fb31893 Generated files from "codesearch-gen-chromium-cronet" build 8694542375723733425, revision 188691d01b1ae989c8a005d75694f1bb90ad9121 by Automatic Generated Files Sync · 66 minutes ago
  4. 4968a06 Generated files from "codesearch-gen-chromium-win" build 8694557502498521857, revision fc6e2990578162ed8127cbe23d5547d9b8dde799 by Automatic Generated Files Sync · 3 hours ago
  5. 8b00040 Generated files from "codesearch-gen-chromium-android" build 8694557502461733985, revision fc6e2990578162ed8127cbe23d5547d9b8dde799 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.