Clone this repo:

Branches

  1. 730bbe5 Generated files from "codesearch-gen-chromium-win" build 8690099344019071937, revision 0fa99d8693aea1c093a65e8a00a503b17037be26 by Automatic Generated Files Sync · 3 hours ago main
  2. 80f33b4 Generated files from "codesearch-gen-chromium-android" build 8690099344633395521, revision 0fa99d8693aea1c093a65e8a00a503b17037be26 by Automatic Generated Files Sync · 3 hours ago
  3. fd5db6c Generated files from "codesearch-gen-chromium-mac" build 8690099344494340017, revision 0fa99d8693aea1c093a65e8a00a503b17037be26 by Automatic Generated Files Sync · 3 hours ago
  4. 15b449ad Generated files from "codesearch-gen-chromium-chromiumos" build 8690099343719630385, revision 0fa99d8693aea1c093a65e8a00a503b17037be26 by Automatic Generated Files Sync · 3 hours ago
  5. f746fbfa Generated files from "codesearch-gen-chromium-linux" build 8690099343980334561, revision 0fa99d8693aea1c093a65e8a00a503b17037be26 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.