Clone this repo:

Branches

  1. 8fb8ef4e Generated files from "codesearch-gen-chromium-webview" build 8725541643709967953, revision 10690c8489dea48e8540d91e173ec124fbad317b by Automatic Generated Files Sync · 19 minutes ago main
  2. ef5415b Generated files from "codesearch-gen-chromium-ios" build 8725541642723483105, revision 10690c8489dea48e8540d91e173ec124fbad317b by Automatic Generated Files Sync · 56 minutes ago
  3. 5bd0929 Generated files from "codesearch-gen-chromium-chromiumos" build 8725555883143139025, revision 1763bc0dd53741f7789e3dba0f4186d4c93a4f5c by Automatic Generated Files Sync · 75 minutes ago
  4. 71ad378 Generated files from "codesearch-gen-chromium-win" build 8725556554402629681, revision 1763bc0dd53741f7789e3dba0f4186d4c93a4f5c by Automatic Generated Files Sync · 2 hours ago
  5. c937503 Generated files from "codesearch-gen-chromium-linux" build 8725556553008190337, revision 1763bc0dd53741f7789e3dba0f4186d4c93a4f5c 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.