Clone this repo:

Branches

  1. 4ef50dc Generated files from "codesearch-gen-chromium-ios" build 8712384811101061137, revision ea15a8a7b753018383ef554638fd2155c6862e62 by Automatic Generated Files Sync · 10 minutes ago main
  2. 1320b94 Generated files from "codesearch-gen-chromium-cronet" build 8712384811342234993, revision ea15a8a7b753018383ef554638fd2155c6862e62 by Automatic Generated Files Sync · 36 minutes ago
  3. 4466a065 Generated files from "codesearch-gen-chromium-android" build 8712405065265239265, revision af146dbc5c1ddfafa95ec10d5a9c2a6c2dd82122 by Automatic Generated Files Sync · 4 hours ago
  4. 5e6dd83 Generated files from "codesearch-gen-chromium-win" build 8712405065151397601, revision af146dbc5c1ddfafa95ec10d5a9c2a6c2dd82122 by Automatic Generated Files Sync · 4 hours ago
  5. 50b0b23 Generated files from "codesearch-gen-chromium-chromiumos" build 8712405064862585313, revision af146dbc5c1ddfafa95ec10d5a9c2a6c2dd82122 by Automatic Generated Files Sync · 4 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.