Clone this repo:

Branches

  1. 22c5b27 Generated files from "codesearch-gen-chromium-mac" build 8680284732425157985, revision e01b725f7fe8e0890561f98cb3befb19ae6946d9 by Automatic Generated Files Sync · 4 hours ago main
  2. bffa294 Generated files from "codesearch-gen-chromium-ios" build 8680284732425158017, revision e01b725f7fe8e0890561f98cb3befb19ae6946d9 by Automatic Generated Files Sync · 4 hours ago
  3. 3c6d2d46 Generated files from "codesearch-gen-chromium-win" build 8680284732425157953, revision e01b725f7fe8e0890561f98cb3befb19ae6946d9 by Automatic Generated Files Sync · 4 hours ago
  4. 5e6f292e Generated files from "codesearch-gen-chromium-fuchsia" build 8680284732425158033, revision e01b725f7fe8e0890561f98cb3befb19ae6946d9 by Automatic Generated Files Sync · 5 hours ago
  5. 1a1a9f3 Generated files from "codesearch-gen-chromium-linux" build 8680284732425158001, revision e01b725f7fe8e0890561f98cb3befb19ae6946d9 by Automatic Generated Files Sync · 5 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.