Clone this repo:

Branches

  1. d5d2229 Generated files from "codesearch-gen-chromium-ios" build 8741305513253165169, revision 52c8632e39b952492b2a9ba9c9c63c3a17b75490 by Automatic Generated Files Sync · 3 minutes ago main
  2. c7f6913 Generated files from "codesearch-gen-chromium-lacros" build 8741320385746558209, revision a9b70cb2bf18ace4273cb731a28b150ccc147d78 by Automatic Generated Files Sync · 30 minutes ago
  3. a2d4ee8 Generated files from "codesearch-gen-chromium-linux" build 8741320386809826145, revision a9b70cb2bf18ace4273cb731a28b150ccc147d78 by Automatic Generated Files Sync · 39 minutes ago
  4. a45a429 Generated files from "codesearch-gen-chromium-win" build 8741320387102583297, revision a9b70cb2bf18ace4273cb731a28b150ccc147d78 by Automatic Generated Files Sync · 60 minutes ago
  5. e6acc01 Generated files from "codesearch-gen-chromium-fuchsia" build 8741320384767444081, revision a9b70cb2bf18ace4273cb731a28b150ccc147d78 by Automatic Generated Files Sync · 88 minutes 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.