Clone this repo:

Branches

  1. 50af0aa Generated files from "codesearch-gen-chromium-webview" build 8747118652625934001, revision 7d09235c0ec75f1db9d00b6402c500a80293279f by Automatic Generated Files Sync · 57 minutes ago main
  2. 02f0cc55 Generated files from "codesearch-gen-chromium-chromiumos" build 8747131775974730017, revision 48ce02f6ccfa848dac7a717a5822f1186df04405 by Automatic Generated Files Sync · 2 hours ago
  3. dbad0a2 Generated files from "codesearch-gen-chromium-ios" build 8747118652914583841, revision 7d09235c0ec75f1db9d00b6402c500a80293279f by Automatic Generated Files Sync · 2 hours ago
  4. 03ad328 Generated files from "codesearch-gen-chromium-lacros" build 8747129347402603745, revision 48ce02f6ccfa848dac7a717a5822f1186df04405 by Automatic Generated Files Sync · 2 hours ago
  5. 4d34f28 Generated files from "codesearch-gen-chromium-android" build 8747134760294045281, revision 331fc448203fbf911f04a820db3edc0594b22130 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.