Clone this repo:

Branches

  1. f11e389 Generated files from "codesearch-gen-chromium-cronet" build 8712676865781862705, revision f72f42b99ea0e3bfada7bc5bcd23952ac6d9e741 by Automatic Generated Files Sync · 14 minutes ago main
  2. 6722770 Generated files from "codesearch-gen-chromium-chromiumos" build 8712691985941250273, revision 6ef6439ba0d7fc7a8ecfef9caa4f614ddc4ddddd by Automatic Generated Files Sync · 2 hours ago
  3. 396b189 Generated files from "codesearch-gen-chromium-win" build 8712691986975759393, revision 6ef6439ba0d7fc7a8ecfef9caa4f614ddc4ddddd by Automatic Generated Files Sync · 3 hours ago
  4. fb33c774 Generated files from "codesearch-gen-chromium-linux" build 8712691986809576209, revision 6ef6439ba0d7fc7a8ecfef9caa4f614ddc4ddddd by Automatic Generated Files Sync · 3 hours ago
  5. 652f52f Generated files from "codesearch-gen-chromium-mac" build 8712691985926596865, revision 6ef6439ba0d7fc7a8ecfef9caa4f614ddc4ddddd by Automatic Generated Files Sync · 3 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.