Clone this repo:

Branches

  1. 7d8d7e9 Generated files from "codesearch-gen-chromium-ios" build 8742634036185097265, revision d3d81be7a4cc61d322045a4471b21399d8747ee4 by Automatic Generated Files Sync · 3 minutes ago main
  2. d42cc7d Generated files from "codesearch-gen-chromium-chromiumos" build 8742646025279858017, revision 3079edabbf94b11f09c8c806bd1ef03e867c1979 by Automatic Generated Files Sync · 8 minutes ago
  3. ff1fd140 Generated files from "codesearch-gen-chromium-cronet" build 8742634035567757297, revision d3d81be7a4cc61d322045a4471b21399d8747ee4 by Automatic Generated Files Sync · 21 minutes ago
  4. 70d9be5 Generated files from "codesearch-gen-chromium-win" build 8742648370151005233, revision 3079edabbf94b11f09c8c806bd1ef03e867c1979 by Automatic Generated Files Sync · 62 minutes ago
  5. daedf73 Generated files from "codesearch-gen-chromium-fuchsia" build 8742649384427800385, revision 3079edabbf94b11f09c8c806bd1ef03e867c1979 by Automatic Generated Files Sync · 81 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.