Clone this repo:
  1. 3111628 Generated files from "codesearch-gen-chromium-chromiumos" build 8779401430114938705, revision 3fe4b9c0ac7573d31aa7d235e39887a2484a0331 by Automatic Generated Files Sync · 38 minutes ago main
  2. d5ec006 Generated files from "codesearch-gen-chromium-fuchsia" build 8779401431612955825, revision 3fe4b9c0ac7573d31aa7d235e39887a2484a0331 by Automatic Generated Files Sync · 61 minutes ago
  3. b5d7881 Generated files from "codesearch-gen-chromium-lacros" build 8779401430722772945, revision 3fe4b9c0ac7573d31aa7d235e39887a2484a0331 by Automatic Generated Files Sync · 70 minutes ago
  4. 01fbcdc Generated files from "codesearch-gen-chromium-linux" build 8779401430982523537, revision 3fe4b9c0ac7573d31aa7d235e39887a2484a0331 by Automatic Generated Files Sync · 73 minutes ago
  5. 877c390 Generated files from "codesearch-gen-chromium-mac" build 8779418552467183009, revision fc63d22817c32fa2db6cae1874f899d06723102a 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.